Sign in
Explore
Skills · SkillEveryday codingPlanning & specsReviewedRuns shell commands

grill-me

Interviews you about a plan one question at a time with a recommended answer for each, exploring the codebase where it can. Adapted from Matt Pocock's grill-me (MIT).

View on GitHub
Kind
Skill
Works with
Claude Code
Source
Claude Skills (Alireza Rezvani) @ e4a1dc369590
Path
engineering/grill-me/skills/grill-me/SKILL.md
Jobs
Requirements interviews
Topics
Planning & specs

Credit

Made by
alirezarezvani
Original
github.com/alirezarezvani/claude-skills/blob/e4a1dc3695908dd5…
License
MIT

Listed by Skill Manifest; not made by us.

InstallInstall it from a plugin marketplace.
/plugin marketplace add alirezarezvani/claude-skills
Install factsScanned 2 Nov 2026
Adds
  • .claude/skills/grill-me/ (the skill folder)
  • 5 file(s) the skill refers to
Runs scripts
Yes
  • Marked in the catalog record
Uses the network
None found
Needs secrets
None found
Source revision
e4a1dc369590
Licence
MIT
Last activity
31 Oct 2026
Review
Reviewed

Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.

  • Only the main file is read; other files in the folder are not scanned
# 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
…