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".
Start a fresh conversation. Replace the highlighted placeholders.
Use the grill-me skill to stress-test this plan or design: [paste your plan or design]. Ask one focused multiple-choice question at a time, explore available project files yourself when they can answer a question, and continue until the decision branches are resolved. Then provide a concise summary of the decisions made.
Required inputs
A plan or design to review, replacing `[paste your plan or design]`
Optional relevant project files or codebase context
Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗
SKILL.md
name: grill-medescription: 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
Use the AskUserQuestion tool for every question you ask. Never pose questions as plain text in your response — always use the multiple-choice popup so the user can quickly select an answer or type a custom one.
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. The user always has the "Other" field available to write something custom.
Flow
After receiving an answer, briefly acknowledge the decision (1–2 sentences max), then immediately ask the next question via AskUserQuestion.
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.