/cook

Inputs

Accept one of:

A spec path. When explicit, read it verbatim wherever it points.
A bare slug. Resolve it to the durable spec path with SPEC=$(python3 shared/scripts/artifact_path.py specs <slug>), then read "$SPEC". If you're on a host that only exposes the packaged helper, python3 ${CLAUDE_SKILL_DIR}/scripts/cook.pyz artifact-path specs <slug> is the fallback. The resolver anchors specs at the per-project durable corpus (see ../cheese/references/formatting.md § Corpus location); this is the form /ultracook uses when chaining.
A pasted spec or issue.
A focused implementation request with acceptance criteria.
A clear, unambiguous task — single-file fix, named bug, well-scoped tweak — even without a spec.

Optional flags:

--auto — autonomous mode: skip every handoff gate and chain /press → /age → /cure (see ## Auto mode below; full selection/cap rules in references/auto-mode.md).
--hard — propagate through /press → /age → /cure → /plate; /plate fires /hard-cheese after its final artifact-writing gate.
--open-pr — propagate to terminal /plate, which follows its explicit-choice and review-shape policy for a new PR.
--resume <slug> — resume a crashed fan run from its manifest (full mechanics: references/fan-pathway.md § --resume).