Menu
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | grilling |
| description | Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases. |
| license | MIT |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
If a fact can be found by exploring the codebase, look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.
During the grilling session, you MUST actively apply the project's documentation standards:
Domain Glossary Integration: If a question resolves ambiguous business terms or introduces new domain entities:
CONTEXT-MAP.md at root first; follow the map to the correct directory, or use root CONTEXT.md)._Avoid_ as defined in .claude/standards/CONTEXT-FORMAT.md.Architecture Decision Records (ADRs): If a decision is a "hard-to-reverse" architectural choice:
.claude/standards/ADR-FORMAT.md: (1) Hard to reverse, (2) Surprising without context, (3) Real trade-off.docs/adr/ using the format defined in .claude/standards/ADR-FORMAT.md. Do not embed the ADR in other documents.Do not enact the plan until I confirm we have reached a shared understanding.
Standardized workflow for discovering, reading, writing, and compacting the project's memory file (memory.instructions.md) to persist context across AI chat sessions, with a permanent Knowledge Base for cross-session decisions and lessons learned.
Performs consistency and traceability audits across documents (PRD vs Spec vs Plan) to detect missing coverage and scope creep.
Systematic codebase exploration, architectural critique, and generation of Project Discovery Drafts for SDLC Phase 0.
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans with rollback strategies.
Helps interrogate Product Requirements (PRD), Technical Specifications, and Implementation Plans to find ambiguities, missing edge cases, and hidden assumptions.
Workflow for auditing, designing, and writing structured documentation based on the Diátaxis Framework (Tutorials, How-to, Reference, Explanation).