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 terminal `/plate`; 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. If `$ARGUMENTS` is missing entirely and there is no recent context to lean on, ask one clarifying question through the host routing guide in [`references/handoff-gate.md`](references/handoff-gate.md) before classifying. ## Flow 0. **Read the full user message, not just `$ARGUMENTS`.** Any prose accompanying the invocation is a directive list; execute or answer it before — and where it conflicts, instead of — the flow's defaults and any handoff protocol. The handoff file restores state; the user's live message overrides it. 1. **Think first (silent).*