grilling

Stress-test plans by interviewing users to resolve or defer every open decision.

2|Updated Jul 24, 2026
One-click install
npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill grilling-konstantinos-malavazos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/konstantinos-malavazos/claude-code-playbook/tree/main/templates/skills/grilling
Command: npx skills add https://github.com/konstantinos-malavazos/claude-code-playbook --skill grilling-konstantinos-malavazos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often hide silent assumptions and unresolved decisions that only surface during implementation, causing rework and stalls. This Skill forces every open question in a plan into the open through a structured one-question-at-a-time interview, so each decision is either answered concretely or explicitly deferred with an owner and a cost. ## Core Features & Use Cases - Decision tree mapping: Maps the plan as a tree of dependent decisions, posting the full numbered question list up front and re-deriving what is askable after every answer. - Disciplined questioning: Enforces one short question per turn with two or three options and a single-reason recommendation, never asking what code search, memory, or research subagents can answer. - Managed deferrals: Every deferred decision gets an owner, a reversal cost, an unblocking plan, and a record in durable ticket state for later resumption. - Use Case: Before implementing a multi-repo feature, run a grilling session to surface the seven decisions the plan assumes, resolve five with the user, and defer two to named owners with documented fallback defaults. ## Quick Start Ask the assistant to grill you on your current plan or design so every open question is resolved or explicitly deferred before implementation begins.

Frequently Asked Questions about grilling

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

FAQPage Schema
How do I stress-test a plan before implementation?

Run a structured interview that maps the plan as a decision tree, posts the full numbered question list up front, then asks one question at a time. Each decision ends as either answered concretely or deferred with a named owner and reversal cost.

What is a decision tree interview for software planning?

It is a technique where every decision in a plan branches into the decisions that depend on it, and only currently answerable questions are asked. After each answer, the set of askable questions is re-derived since answers can add, close, or invalidate branches.

When should I defer a decision instead of answering it?

Defer when the answer belongs to a person or spec that does not exist yet. A valid deferral names an owner, prices the cost of guessing wrong, plans around it so independent work proceeds, and records the open question in durable ticket state.

Can research subagents answer questions during a planning interview?

Yes. Questions about code facts, external APIs, or specs are dispatched to research subagents rather than asked of the user. The interview continues with independent questions while the lookup runs, and only downstream branches wait for the result.

What are the limitations of interview-based plan validation?

It only resolves decisions requiring human judgement; it cannot settle questions that need running code or external facts without supporting tools. It also depends on the user confirming shared understanding before the plan is acted on.