grill-me

Interrogates plans and decisions through Socratic questioning and records outcomes as numbered ADRs.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/mistakenot/skills --skill grill-me-mistakenot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/mistakenot/skills/tree/main/plugins/grill-me/skills/grill-me
Command: npx skills add https://github.com/mistakenot/skills --skill grill-me-mistakenot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Plans, designs, and decisions often rest on hidden assumptions and unexamined trade-offs that only surface after costly implementation. This Skill pressure-tests your thinking through relentless Socratic questioning before you commit to hard-to-reverse choices. ## Core Features & Use Cases - Structured Interrogation: Runs multi-round questioning using the AskUserQuestion tool with recommended answer options, mapping 4-8 risk facets before drilling into the highest-value threads. - Decision Recording: Writes numbered Architecture Decision Records (ADRs) in docs/adr/ for decisions that are hard to reverse, surprising, and involve real trade-offs. - Append-Only Grilling Log: Preserves every question and answer in docs/grilling/grilling-log.md so reasoning is never lost and sessions can resume later. - Use Case: Before committing to an event-sourced architecture for your order system, get grilled on load assumptions, failure modes, and reversibility — then receive ADRs documenting why each call was made. ## Quick Start Ask the agent to grill you on your plan for the new sync feature before you start implementing it.

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 software design before implementing it?▼

Invoke the grill-me skill with your plan or design as the subject. It maps 4-8 risk facets, asks targeted questions in rounds of 3-6 using concrete scenarios, and records settled decisions as numbered ADRs in docs/adr/.

What is an Architecture Decision Record and when should I write one?▼

An ADR is a short numbered document in docs/adr/ capturing a decision and its rationale. Write one only when a decision is hard to reverse, surprising without context, and the result of a real trade-off — everything else stays in the grilling log.

When should I use grill-me instead of brainstorming or task planning?▼

Use grill-me to pressure-test an existing plan, design, or decision — not to generate new ideas (use generate-10-ideas) or plan routine tasks (use new-task). It is adversarial toward the idea, sharpening what already exists.

Does grill-me require a project glossary or existing documentation?▼

No. It optionally reads docs/concepts/UBIQUITOUS_LANGUAGE.md for canonical terms and checks docs/adr/ for prior decisions, but works fully without either. The grilling log and ADR directories are created lazily on first use.

What happens to the questions and answers after a grilling session?▼

Every question-answer pair is appended to docs/grilling/grilling-log.md with a dated context line, never rewritten. ADR-worthy decisions are additionally written as numbered files in docs/adr/, and each session closes with a summary of decisions, accepted risks, and open questions.