| name | grill-me |
| description | Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". |
Interview the user relentlessly about every aspect of their plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
How to ask questions
Ask one question at a time. Wait for the user's answer before moving to the next question. This keeps the conversation focused and prevents overwhelm.
For each question, provide 2–4 concrete multiple-choice options representing the most likely answers or directions. Think about what the user would realistically choose — generic options like "Yes" / "No" aren't helpful unless the question is genuinely binary. Always include an "Other" option so the user can write a custom answer.
Use the platform-native question/interaction tool when available:
- Claude Code / Cursor / Cowork: use
AskUserQuestion.
- OpenCode: use the
question tool.
- Copilot CLI: use the
ask or interactive prompt tool.
- Codex: use the platform's user-input tool (e.g.,
confirm / input).
- Fallback / no tool available: print the question as plain text with numbered options and a clear prompt for the user to reply with the number or custom answer.
Never pose questions as plain text in your response when a question tool is available.
Flow
- After receiving an answer, briefly acknowledge the decision (1–2 sentences max), then immediately ask the next question.
- If a question can be answered by exploring the codebase or files, explore them yourself instead of asking the user.
- Continue until all branches of the design tree are resolved.
- When finished, provide a concise summary of all decisions made.
