Ultracook
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.
- Skill ID
- paulnsorensen/easy-cheese/ultracook
- Publisher
- paulnsorensen
- Repository
- easy-cheese
- Installs
- 0
- Files
- 8
- License
- MIT
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
paulnsorensen/easy-cheese/ultracookInstalls these files- SKILL.md
- references/curd-prompt.md
- references/decomposer-prompt.md
- references/manifest-schema.json
- references/pr-plan-schema.json
- references/pr-planner-prompt.md
- references/spawn-primitive-reference.md
- references/wiring-prompt.md
What this skill tells the agent
/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`'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 incook.pyz, and noultracook.pyzbundle is published.- The manifest path stays
.cheese/ultracook/<slug>/manifest.yamlfor continuity — the identity of the skill that reads/writes it changed, not the path; its shape isreferences/manifest-schema.json, and each curd's dispatch prompt isreferences/curd-prompt.md, both read by/cook's fan pathway. src/easy_cheese/shared/fanout/mode.pyremains a decomposer/fanout internal —/cook's fan pathway calls it 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` same as everywhere else.
If you are here because muscle memory typed /ultracook, run /cook with the same arguments.
More from paulnsorensen
Use this skill in a project
Open any RiverX project, search the Skills panel for paulnsorensen/easy-cheese/ultracook, and install it in one click.