cheese

/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.

Flow

1. Read the full user message, not just $ARGUMENTS. Treat all other user prose as a directive list. Follow live directives instead of conflicting defaults or the handoff protocol. The handoff file restores state. The user's live message overrides it. Exception: a live directive never waives a resume integrity gate. Ambiguity, unresolved lineage, an integrity finding, and status: gated: still stop dispatch. A live directive answers only the informed trust gate for a clean legacy result. references/continue-resume.md owns these gates.
2. Think first (silent). Model the problem internally per skills/culture/SKILL.md — restate the ask, list candidate targets, name the deciding signal. Output is the classification that drives step 2.
3. Classify — match $ARGUMENTS against the intent shapes in references/classification.md. Pick the highest-confidence shape; below the threshold, route to clarify (handled by the tier-3 escalation in step 4).
4. Clarity check (cook intents only). Run Cook's fast-path check for a cook intent. Dispatch a mold intent to /mold's user mode instead. Direct plate intents bypass this check.
5. Escalate when needed. Tier 1 dispatches the chosen target. It uses /mold's agent mode when /cook --auto needs a specification. Tier 2 invokes /culture or /briesearch internally, then repeats the clarity check. Tier 3 blocks on a single targeted host-routed question. Classify the answer again. See ## Escalation.
6. Ground the wiki when hallouminate is present and the route is escalated. Derive a query from the input. Skip this step on the fast path. A fast route grounds nothing and spends no probe. Make at most one grounding call against the wiki corpus. Resolve the corpus through the corpus listing tool first. Resolve both tool names through references/optional-plugins.md. That reference matches the capability, because each host prefixes the names differently. Use the probe shape in skills/mold/references/grounding.md. Add the best hits to handoff_context.wiki_hits as [{page, line, why}]. See references/handoff-gate.md section Context payloads. When no wiki corpus exists, use references/optional-plugins.md.
7. Announce — print a short block (Intent / Reason / Target, plus wiki hits when present) per the format in ## Output. Cite the signal that drove the routing decision.
8. Self-check — run the coherence questions in references/coherence-check.md. If any fails, downgrade to clarify (tier 3) or research.
9. Dispatch. Without --safe, run the chosen skill and its context packet after the announcement. With --safe, issue a handoff gate from references/handoff-gate.md. Pre-select the recommended target, include an alternative, and put Stop last. Wait for the user's selection before dispatch.