grill-me

Conducts a Socratic interview to resolve open design decisions one question at a time.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/mikestopcontinues/agent-skills --skill grill-me-mikestopcontinues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/mikestopcontinues/agent-skills/tree/main/claude/skills/grill-me
Command: npx skills add https://github.com/mikestopcontinues/agent-skills --skill grill-me-mikestopcontinues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs and plans often contain unresolved questions that surface too late. This Skill stress-tests a plan or design through a structured interview, walking the decision tree branch by branch until every open question is answered and persisted. ## Core Features & Use Cases - Socratic Interview Loop: Asks one question per turn, always with a grounded recommendation based on codebase exploration, and waits for the captain to lock an answer. - Dependency-Ordered Questioning: Maps the decision tree internally so parent decisions are resolved before dependent child questions. - Outcome Persistence: Routes locked answers to /create-decision and non-decision observations to /create-note, keeping a durable record of the interview. - Use Case: Before writing a spec for a new feature, say "grill me on the caching design" to converge on every open choice — storage backend, TTL policy, invalidation strategy — with each resolution saved as a decision record. ## Quick Start Ask the assistant to grill you on your current plan or design, for example by saying "grill me on the authentication design".

Frequently Asked Questions about grill-me

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a design before writing a spec?▼

Start a grill-me interview by naming the topic, such as "grill me on the API design". The skill asks one question per turn with a codebase-grounded recommendation, and each answer you lock is saved as a decision record.

What is the difference between grill-me and lock-decisions?▼

grill-me is open-ended and discovers questions as the interview unfolds, while lock-decisions consumes a finite list of decision-shaped findings. lock-decisions can route a finding to grill-me and then resume its own loop.

How are interview outcomes saved during a design review?▼

Locked answers to design questions are persisted via /create-decision with the captain's resolution and rationale. Observations that are not decisions, such as API quirks or constraints, are saved via /create-note.

When should I not use a Socratic interview for decisions?▼

Avoid it when you have a finite list of findings to resolve (use lock-decisions), when you need current repo state (use start-session), or when you want to author or revise a document (use write-doc or revise-doc).

Does the interview ask multiple questions at once?▼

No. The skill enforces one question per turn so the dependency graph of decisions stays legible, and it replans the question queue whenever a parent answer reshapes the child questions.