The command set — the named jobs Skippy and every agent already know how to do.

a recipe is a written set of instructions an assistant picks up the moment a job matches it — plan this build, design this screen, write Anatoly's post, check this is safe.

As of September 10, 08:02 PM
What the status words mean proven · done, not independently checked · partly done · not started · blocked · parked
0%not started

22 steps: 0 proven · 0 partly done · 22 untouched · 0 blocked · 0 parked

agent runs · not recordedtokens used · not recordedreview notes · not recordeddollars charged · not recorded

The plan as first written

Steps

IdPlain wordsPercentStateProofWhat is left
1Write down what is actually on the shelf today0% not startedNode projects/ops/skippy-jobs/_test-skill-pointers.mjs — full output recorded, plus a SEPARATE PINNED count for each of the four named shelves (ZION/skills/, .claude/skills/, ~/.agents/skills/, ~/.claude/skills/) with its shortcut, separate-copy, has-test and no-test sub-counts, and the published page's baseline captures and anchor map, all saved with the timestamp of the readThe step
2One command that produces the reading, with a deliberate break to prove it can come back red0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case all — every named case passes and exits 0; the sabotage control exits non-zero naming the assertion it broke, then returns to 0 on reversal; the library-layout case §2d names is among themThe step
3The inventory, as one file0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case inventory — one row per recipe on each of the four named shelves with all seven fields filled, each shelf's row count equal to step 1's pinned number for it, and a recipe added and another removed on the fixture shelf both visible on the next runThe step
4Prove the recipes an agent needs are really in front of it0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case loading — four cold-helper probes through both doorways recorded verbatim, the two directions (a recipe arriving unasked, and a recipe asked for by name) reported separately rather than as one verdict, each recipe stated as arriving on its own or needing to be pasted by hand, and a control naming a recipe on no shelf coming back negativeThe step
5Repair every dead link inside a live recipe0% not startedNode projects/ops/skippy-jobs/_test-skill-pointers.mjs — exits clean over every shelf; a deliberately broken path turns it red naming the recipe and the line, then green on reversal; each recipe's line count before and after is recorded with every removed line quoted and its reason, read by the checker rather than only the exit code; git status shows each edited real ZION file as modified and the .claude shortcut as unchangedThe step
6Fix the settings block that is not being honoured0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case frontmatter — the fault is reproduced and recorded before anything changes, then repaired and re-measured; a failure to reproduce closes the step on that measurement and corrects the noteThe step
7Take the three dead recipes out of the menu, keep their files as signposts0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case menu — a fresh session's menu names none of the three on any shelf, all three files are still on disk with their banners, and the two changes made outside the repository (~/.claude/skills/shopping-list and ~/.agents/skills/shopping-list) are recorded as machine-localThe step
8The month-old copies of the planning rules stop sitting where a reader can pick the wrong one0% not startedFor EACH of .claude/skills/plan/SKILL.md.bak-2026-08-28-postmortem and .claude/skills/plan/references/failure-registry.md.bak-2026-08-28-postmortem, both halves run and recorded separately: test ! -e <path> proves it gone from the working tree, and git cat-file -e HEAD:<path> exits 0 proving it still resolves at the last commit; the named archive SKILL-ARCHIVE-2026-08-27.md is untouched and the live planning recipe is unchangedThe step
9One copy of every recipe, so an edit reaches every machine0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case copies — the redesign recipe's real file now sits at ZION/skills/design-redo/, the loading shelf's entry is a shortcut to it, an edit made at the real path reads back through that shortcut and shows as modified in git, and the four the writing lane owns are recorded as owned with the decision they wait onThe step
10Find out why some recipes load with no description, and fix the cause0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case descriptions — the cause is named PER ENTRY from a measurement rather than guessed, every affected entry shows a description in a fresh session's menu, a deliberately emptied description comes back red, and git status shows each edited real ZION file as modified and the .claude shortcut as unchangedThe step
11Every recipe with no pass list gets one, including Nick's own and the required outside ones0% not startedNode projects/ops/skippy-jobs/_test-skill-evals.mjs — passes over the whole set; on each of the four shelves the count of recipes carrying a written test equals step 1's pinned count for that shelf; the grader produces a counted result against each new test rather than an honest refusal for want of one; and the tests written outside the repository are recorded as machine-localThe step
12Correct the public list so it names exactly what exists0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case library and --case library-layout — the page's rows match the reading row for row, the count is right, and the design fidelity gate reports zero mismatched properties, zero unmeasured anchors and zero rows in disagreement; the proof names all four required things: the check command with its counts, the side-by-side image filenames, the creative director's verdict and the independent verifier's verdictThe step
13The redesign recipe reaches the non-Anthropic doorway, so the same job meets the same standard0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case doorways — the second doorway offers every recipe on the main shelf, in that ONE direction only with the vendor-installed set named as an explicit exemption and never copied into this repository, every addition is a shortcut rather than a copy, removing a main-shelf entry on the fixture shelf comes back red, and the change outside the repository is recorded as machine-localThe step
14The dead-link and inventory checks run every round by themselves0% not startedNode projects/ops/skippy-jobs/_test-no-unrun-tests.mjs — clean; both checks in the round's discovered set; a deliberately broken pointer makes the round red and green again on reversalThe step
15Every recipe graded once so it carries a real date instead of 'written, never proven'0% not startedNode projects/ops/skippy-jobs/grade-skill-evals.mjs --json — a result for every recipe on all four shelves counted against step 1's four pinned numbers, including Nick's own shortcuts and the required search and security recipes: a counted date, or an honest refusal naming why — and 'could not grade — no written test' is NOT accepted for any recipe on step 11's covered list, which fails back to step 11 rather than closing here; the main shelf byte-identical before and afterThe step
16The check that stops the grader passing something it never read is proved to work0% not startedNode projects/ops/skippy-jobs/_test-grade-skill-evals.mjs — clean on the real grader, red when the grader is made to pass a recipe whose run it could not read, green again on reversalThe step
17Fold anything stale or duplicated into one, with the reason written down0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case consolidation — the reading afterwards shows one entry where the agreed consolidation named two, nothing is deleted, and every consolidation is written into NOTES.txt with its date and reasonThe step
18The rewritten planning rules go live, carrying the progress-screen ruling0% not startedPython3 projects/ops/agents/check_plan.py --selftest and node projects/ops/skippy-jobs/lib/check-plan-gate.mjs --selftest both pass after the landing, and the landed file's fingerprint matches the one Nick approvedWaiting on Nick: — his approval of the rewritten planning rules before they go live. They are written and machine-checked in their own lane; nothing lands them but his word. Every other step runs regardless and this one is visibly held until it arrives
19The four writing recipes become one copy each, once Nick has said whether the drafts sound like Anatoly0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case copies — no entry left recorded as owned elsewhere; NICK'S OWN DATED WORDS read from the Jasmin lane's record, not a lane verdict; the two versions compared word for word before the collapse; each surviving real file moved onto the main shelf before its shortcut is madeWaiting on Nick: — his own words on whether a draft sounds like Anatoly. He ruled on 2026-09-08 at 14:05 EST that nothing goes to Anatoly until he says a draft sounds like him, so no live client-voice recipe is promoted on any record but his. This step is visibly held with that one question and every other step runs regardless
20The weekly re-check happens inside Larry's weekly review — one clock, one heartbeat0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --case weekly — the reading, the pointer check and the graded dates re-taken inside Larry's weekly review on its one clock; an aged fixture raises a plain-English alarm naming the recipe; a deliberately skipped review is reported rather than read as health; no second timer existsThe step
21The weekly grading lives inside Larry's weekly review, not on a timer of its own0% not startedNode projects/ops/skippy-jobs/jobs/grade-skill-evals.mjs — runs unattended as part of Larry's weekly review, its first run puts a real date on at least one recipe, and the registered set shows the grading once, inside that review and nowhere elseThe step
22Someone who built none of it reads the whole shelf again and says whether they agree0% not startedNode projects/ops/skippy-jobs/_test-skill-inventory.mjs --read-only-live outcomes — the closing reading taken from all four real shelves, reconciled against step 1's four pinned counts, and compared row for row against step 3's, with both readers' verdicts recorded side by sideThe step

Done

0 of 22 steps proven

Left

22 of 22 steps not yet proven

Blocked on

  • Nothing currently blocked.

Formal remaining plan

#StepNeeds Nick
1Write down what is actually on the shelf todayNo
2One command that produces the reading, with a deliberate break to prove it can come back redNo
3The inventory, as one fileNo
4Prove the recipes an agent needs are really in front of itNo
5Repair every dead link inside a live recipeNo
6Fix the settings block that is not being honouredNo
7Take the three dead recipes out of the menu, keep their files as signpostsNo
8The month-old copies of the planning rules stop sitting where a reader can pick the wrong oneNo
9One copy of every recipe, so an edit reaches every machineNo
10Find out why some recipes load with no description, and fix the causeNo
11Every recipe with no pass list gets one, including Nick's own and the required outside onesNo
12Correct the public list so it names exactly what existsNo
13The redesign recipe reaches the non-Anthropic doorway, so the same job meets the same standardNo
14The dead-link and inventory checks run every round by themselvesNo
15Every recipe graded once so it carries a real date instead of 'written, never proven'No
16The check that stops the grader passing something it never read is proved to workNo
17Fold anything stale or duplicated into one, with the reason written downNo
18The rewritten planning rules go live, carrying the progress-screen rulingYes
19The four writing recipes become one copy each, once Nick has said whether the drafts sound like AnatolyYes
20The weekly re-check happens inside Larry's weekly review — one clock, one heartbeatNo
21The weekly grading lives inside Larry's weekly review, not on a timer of its ownNo
22Someone who built none of it reads the whole shelf again and says whether they agreeNo

Decisions this lane is waiting on

  1. None.