grill · v2.0.0 · 2026-10-14 · sha256 6280b68c03cc421e
grill v2.0.0A
Immutable. This exact content never changes and is served at /api/v1/blob/6280b68c03cc421e.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_6rvnwzhglxfl4g2l/6280b68c03cc421e92dce73985f4bd0548d31add95108baa29005adf7c397a25.json
Then /plugin install grill@markdownregistry-6rvnwzhglxfl4g2l in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: grill version: 2.0.0 description: Clarify an ambiguous feature or design through direct questions before work is queued. Resolve consequential decisions and preserve only durable intent. disable-model-invocation: true argument-hint: "[topic]" recommended: true --- # Grill Clarify the outcome, boundaries, and decisions needed to make work actionable. Do not build or publish tickets. Read repo instructions and relevant code first. Consult relevant parts of CONTEXT/glossary.md, CONTEXT/architecture.md, and CONTEXT/adr/ when present. Follow CONTEXT-MAP.md in a multi-context repo. Find observable facts yourself. Use a short experiment for an empirical fork when it fits the requested scope. Ask the user about product intent, preferences, or trade-offs an experiment cannot settle. Present distinct options and a recommendation for consequential architectural choices. Ask independent questions together; settle prerequisites before dependent questions. Stop when outcome, acceptance, constraints, and important unresolved risks are clear enough to proceed. An exhaustive implementation interview is unnecessary. Record only information a fresh agent could otherwise get wrong. Update the relevant decision in CONTEXT/architecture.md; define a term in CONTEXT/glossary.md only when outsiders would misunderstand it. Create an ADR only for a hard-to-reverse, surprising decision with a real trade-off. Preserve unrelated prose and create files lazily. Never write CONTEXT/progress.md, a pipeline backlog, or another owner's handoff. Code and checks establish behavior; issues hold task intent and shared status; decision docs preserve rationale. Return the agreed outcome, acceptance, boundaries, and remaining decisions. Suggest /issues when queued work is wanted. A clear small task can go straight to /ship. Stage invocation does not authorize the next stage or an external write.