Help us improve
Share bugs, ideas, or general feedback.
From claude-superskills
Conducts relentless Socratic interviews to stress-test plans, designs, or ideas by walking every decision branch and resolving one-by-one. Triggers only on explicit 'grill me' or 'me grille'.
npx claudepluginhub ericgandrade/claude-superskills --plugin claude-superskillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/claude-superskills:grill-meThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Stress-test a plan, design, or idea through relentless Socratic questioning. Walk down every branch of the decision tree, resolve dependencies between decisions one-by-one, and reach a shared understanding where no assumption is left unchallenged.
Grills users relentlessly on plans, designs, or ideas via Socratic questioning to expose assumptions, gaps, dependencies, and edge cases until shared understanding. Use to stress-test thinking before implementation.
Interviews users on plans and designs via structured Socratic questioning to stress-test ideas, probe assumptions, expose edge cases, and validate feasibility.
Grills users relentlessly on plans or designs by interviewing branch-by-branch through decision trees to reach shared understanding. Use for stress-testing ideas or 'grill me'.
Share bugs, ideas, or general feedback.
Stress-test a plan, design, or idea through relentless Socratic questioning. Walk down every branch of the decision tree, resolve dependencies between decisions one-by-one, and reach a shared understanding where no assumption is left unchallenged.
Trigger ONLY when the user explicitly uses the word "grill" — e.g.:
Do NOT trigger for synonyms or near-misses, even when the intent seems similar:
Read the plan, design, or idea the user has provided. If working in a codebase, explore relevant files before asking questions that can be answered by reading the code.
Before asking the first question, mentally map:
Ask one question at a time. For each question:
Work through branches systematically — exhaust one thread before opening another. When an answer reveals a new sub-question, follow it immediately.
Question types to cycle through:
When all branches of the decision tree are resolved, summarize: