grill-me

# Grill Me $ARGUMENTS Interview relentlessly about every aspect of the plan until reaching shared understanding. ## Usage ``` /grill-me [plan or design to stress-test] ``` ## What This Command Does 1. **Reads** the plan or design (from context, file, or user description) 2. **Walks** down each branch of the decision tree 3. **Resolves** dependencies between decisions one-by-one 4. **Provides** recommended answers for each question 5. **Continues** until shared understanding is reached ## Rules - **MUST** ask questions one at a time — batching defeats the Socratic process - **MUST** provide a recommended answer with every question so the user can accept, refine, or reject - **NEVER** settle for vague or hand-wavy answers — press for specifics ("what does 'scale' mean here — 10k req/s or 10M?") - **NEVER** skip ahead before the current branch is resolved — dependencies between decisions matter - **CRITICAL**: if a question can be answered by **exploring the codebase**, explore instead of asking. Do not outsource verifiable facts to the user. - **MANDATORY**: apply Devil's Advocate critique to every major decision — the default answer ("let's ship it") is almost always the one that needs challenging ## Gotchas - Grilling can feel adversarial. Frame questions as "what if X happens" not "your plan is wrong because X" — the goal is shared understanding, not winning. - Fatigue kicks in around 10 questions deep. For larger plans, pause and summarize every ~7 questions so th...