Retired — /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.

/ultracook (retired) /ultracook is retired as a top level skill. Its mechanics — decompose, wave fan curds, harvest, wire, post merge review, plate — now live inside /cook 's single pathway, dispatched via /cook auto , each phase still running as a fresh, isolated sub agent context blind to the prior phase's reasoning. See [ ../cook/SKILL.md ](../cook/SKILL.md)'s Fan pathway section. Redirect Any /ultracook <spec [flags] invocation resolves to /cook <spec [flags] . Carry open pr , resume <slug , and auto forward verbatim — their semantics are unchanged, just hosted inside /cook now. What did not move skills/ultracook/references/ remains as compatibility material for /cook 's fan pathway; executable runtime now ships only in cook.pyz , and no ultracook.pyz bundle is published. The manifest path stays .cheese/ultracook/<slug /manifest.yaml for continuity — the identity of the skill that reads/writes it changed, not the path; its shape is references/manifest schema.json , and each curd's dispatch prompt is references/curd prompt.md , both read by /cook 's fan pathway. src/easy cheese/shared/fanout/mode.py and src/easy cheese/shared/fanout/curd block.py remain decomposer/fanout internals — /cook 's fan pathway calls them directly rather than through this retired skill. The retained scripts/references still do source code I/O under /cook 's ownership — that follows [ code intelligence routing.md ](../cheese/references/code intelligence routing.md) same as everywhere else. If you are here because muscle memory typed /ultracook , run /cook with the same arguments.