grill-me · alirezarezvani — Claude Code skill: what it does, how to install
Stress-tests project plans and design docs through a disciplined question-and-answer interview to resolve decisions before coding.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install grill-me@claude-code-skillsWhat grill-me does
This skill runs an in-depth interview to test a proposed plan or design. It breaks the document into branches using scripts/decision_tree_extractor.py, prepares questions with recommended answers via scripts/question_generator.py, and logs choices with scripts/grill_session_tracker.py. If a question can be answered from the codebase, the agent checks the repository first using file reads or grep.
The interview enforces strict constraints: one question at a time, depth-first branch resolution, and tracked dependencies. It also includes the cs-grill-master agent and the /cs-grill-me command. This skill is worth running before major refactors or new features when you need all architectural choices locked in early.
What it helps with
- stress-test design documents before writing code
- resolve decision branches depth-first without skipped dependencies
- avoid unnecessary questions by checking the codebase first
- log and lock in final architecture choices
Example prompts for the agent
- grill me on this design proposal
- /cs-grill-me docs/auth-plan.md
- Stress-test my migration plan in plan.md
How to install grill-me
1Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install grill-me@claude-code-skillsThis installs the whole grill-me plugin with all its skills
2Skills CLI (Vercel)
npx skills add alirezarezvani/claude-skills --skill grill-me -a claude-code3Manually: put the files in place
~/.claude/skills/grill-me/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/grill-me/
Manually: put the files in place
.agents/skills/grill-me/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/grill-me/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install alirezarezvani/claude-skills grill-me2Manually: put the files in place
.github/skills/grill-me/SKILL.mdPlatform CLI
gemini skills install https://github.com/alirezarezvani/claude-skills --path engineering/grill-me/skills/grill-meManually: put the files in place
.devin/skills/grill-me/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set349
The whole set →Other versions of grill-me
Similar
Questions about grill-me
How do I install grill-me in Claude Code?
Run /plugin install grill-me@claude-code-skills or install it with npx skills add alirezarezvani/claude-skills --skill grill-me -a claude-code.
What does the grill-me skill do?
It interviews you about a plan one question at a time, provides recommended answers, and walks down decision branches until shared understanding is reached.
How does grill-me handle information already in the repo?
The skill searches the codebase first using tools like grep or file inspection. It only asks the developer if the answer cannot be determined from existing code.
Source text
SKILL.md · MIT
--- 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. 3. **Explore the codebase before asking.** If `grep` / `Read` resolves it, do that first. Saves a turn. 4. **Walk the tree depth-first.** Finish a branch before opening another. 5. **Track dependencies.** If decision B depends on decision A, ask A first. ## Workflow 1. User provides a plan or design (or path to one). 2. Run `scripts/decision_tree_extractor.py` to extract branches. 3. Run `scripts/question_generator.py` to produce the question list with recommendations. 4. Start a session: `scripts/grill_session_tracker.py --action start`. 5. Walk the tree, one question at a time, recording answers in the session. 6. When all branches resolved: report "shared understanding reached" + the locked-in decisions. ## Output Pattern Per question turn: ``` Q[i]/[total]: [question] Recommended answer: [your call + 1-sentence rationale] (Or: I explored the codebase and found [evidence]. Confirm?) ``` ## Tooling See [references/companion_tooling.md](references/companion_tooling.md). Tools: extractor + generator + tracker. Agent: `cs-grill-master`. Command: `/cs-grill-me`. --- **Version:** 1.0.0 **Derived:** Matt Pocock (MIT) + this repo's wrapper
© Alireza Rezvani · MIT · alirezarezvani/claude-skills