grilling

Interrogates plans and decisions through structured rounds of numbered questions.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/jordizle/claude-skills --skill grilling-jordizle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilling
Source: https://github.com/jordizle/claude-skills/tree/main/grilling
Command: npx skills add https://github.com/jordizle/claude-skills --skill grilling-jordizle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and design decisions often contain hidden assumptions and unresolved dependencies that surface too late. This Skill stress-tests an idea by interviewing the user relentlessly until every decision in the design tree is explicitly settled. ## Core Features & Use Cases - Design Tree Mapping: Models a plan as a tree of decisions where each choice branches into dependent sub-decisions. - Frontier-Based Rounds: Asks only the questions whose prerequisites are already settled, numbering each one and providing a recommended answer. - Fact-Finding via Sub-Agents: Dispatches sub-agents to look up environmental facts instead of asking the user for anything discoverable. - Use Case: Before implementing an ambiguous feature, run a grilling session to expose every open design question, settle them round by round, and reach a confirmed shared understanding before writing code. ## Quick Start Ask the assistant to grill you on your plan for the new feature until every design decision is settled.

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 design plan before implementation?

Use a grilling session that maps your plan as a design tree and interviews you in rounds. Each round asks every question whose prerequisites are settled, with recommended answers, until no assumptions remain unexamined.

What is the design tree approach to decision making?

The design tree models every decision as a node branching into dependent sub-decisions. The frontier is the set of questions answerable now; settled answers push the frontier outward and unblock dependent questions in later rounds.

When should I use grilling instead of direct implementation?

Use grilling when a feature or plan is ambiguous and key design decisions are unsettled. Well-defined tasks with settled designs can skip interrogation and go straight to implementation.

Does the grilling process look up facts automatically?

Yes. When a question needs a fact from the filesystem or environment, a sub-agent is dispatched to find it rather than asking the user. Only downstream questions wait on the result; the rest of the frontier proceeds.

When does a grilling session end?

The session ends when the frontier is empty, meaning every branch of the design tree has been visited and nothing is silently assumed. No action is taken until the user confirms shared understanding.