cheeselisted

# /cheese ## Inputs Accept anything the user supplies as `$ARGUMENTS`: - A natural-language feature description, idea, or question. - A spec path (`.cheese/specs/<slug>.md`) or pasted spec content. - A bug report, stack trace, failing test output, or reproduction steps. - A file path, glob, or directory. - A PR or issue reference (`PR#142`, `#87`, GitHub URL). - A research question about an external library, API, or pattern. - An empty or near-empty prompt — treat as "what's next?" and clarify. Optional flags: - `--safe` — gate dispatch behind a confirmation prompt. - `--open-pr` — propagate through the implementation chain to `/cure`. `/cure` consumes this flag and sends the publication intent to terminal `/plate`. `/plate` accepts no `--open-pr` flag of its own. A new PR follows `/plate`'s explicit choice and review shape policy. - `--continue <slug-or-note-path>` — resume an in-flight pipeline from a handoff slug or note. - `--hard` — propagate to `/plate`, which runs the final artifact-writing gate before `/hard-cheese` and publication. - `--reground` — use with `--continue` only. Adversarially re-check the handoff claims before phase dispatch. If `$ARGUMENTS` is missing, ask one clarifying question through the host routing guide. Use [`references/handoff-gate.md`](references/handoff-gate.md). ## Flow 0. **Read the full user message, not just `$ARGUMENTS`.** Treat all other user prose as a directive list. Follow live directives instead of conflicting defa