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 the...
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".
Install
Quick install
npx skills add https://github.com/alirezarezvani/claude-skills/tree/main/engineering/grill-me/skills/grill-menpx skills add alirezarezvani/claude-skills --skill grill-me --agent claude-codenpx skills add alirezarezvani/claude-skills --skill grill-me --agent cursornpx skills add alirezarezvani/claude-skills --skill grill-me --agent codexnpx skills add alirezarezvani/claude-skills --skill grill-me --agent opencodenpx skills add alirezarezvani/claude-skills --skill grill-me --agent github-copilotnpx skills add alirezarezvani/claude-skills --skill grill-me --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add alirezarezvani/claude-skills --skill grill-meManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/alirezarezvani/claude-skills.gitcp -r claude-skills/engineering/grill-me/skills/grill-me ~/.claude/skills/Grill Me
Derived from Matt Pocock's 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)
- One question per turn. Never bundle.
- Provide a recommended answer with each question. Defaulting to "what do you think?" is lazy.
- Explore the codebase before asking. If
grep/Readresolves it, do that first. Saves a turn. - Walk the tree depth-first. Finish a branch before opening another.
- Track dependencies. If decision B depends on decision A, ask A first.
Workflow
- User provides a plan or design (or path to one).
- Run
scripts/decision_tree_extractor.pyto extract branches. - Run
scripts/question_generator.pyto produce the question list with recommendations. - Start a session:
scripts/grill_session_tracker.py --action start. - Walk the tree, one question at a time, recording answers in the session.
- 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
SKILL.md source
--- 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 the... --- # 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
Related skills 6
caveman
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
secure-linux-web-hosting
Use when setting up, hardening, or reviewing a cloud server for self-hosting, including DNS, SSH, firewalls, Nginx, static-site hosting, reverse-proxying an app, HTTPS with Let's Encrypt or ACME clients, safe HTTP-to-HTTPS redirects, or optional post-launch network tuning such as BBR.
readme-i18n
Use when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized README variants in a GitHub-style repository.
lark-shared
Use when first setting up lark-cli, running auth login, switching user/bot identity (--as), handling permission denied or scope errors, needing to update lark-cli, or seeing _notice in JSON output.
improve-codebase-architecture
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
paper-context-resolver
Optional RigorPilot helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacin...