/grill-me
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".
One skill from claude-skills.
shell
$ npx -y skills add alirezarezvani/claude-skills --skill grill-me --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/grill-me
Context preview
The summary Claude sees to decide when to auto-load this skill.
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".
Stats
Stars23,058
Forks3,139
LanguagePython
LicenseMIT
Ships with claude-skills
SKILL.md
grill-me.SKILL.md
--- 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". license: MIT metadata: derived_from: "https://github.com/mattpocock/skills/tree/main/skills/productivity/grill-me" original_author: "Matt Pocock (@mattpocock)" original_license: MIT voice: "Matt Pocock — relentless, one-at-a-time, explores-codebase-first" version: 1.0.0 --- # Grill Me > Derived from [Matt Pocock's grill-me](https://github.com/mattpocock/skills/tree/main/skills/productivity/grill-me) (MIT). Matt's interview discipline preserved verbatim. Additions: extraction + question + session tools + references + cs-* wrapper (see [references/companion_tooling.md](references/companion_tooling.md)). 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. If a question can be answered by exploring the codebase, explore the codebase instead. ## Rules (preserved + amplified) 1. **One question per turn.** Never bundle. 2. **Provide a recommended answer with each question.** Defaulting to "what do you think?" is lazy.
