Grilling

Grilling interviews the user relentlessly about every aspect of a plan or design until reaching a shared understanding. It walks down each branch of the design tree, resolving dependencies between decisions one by one, and for every question it asks, it also offers its own recommended answer rather than leaving the user to guess what a good answer looks like.

Use it when the user wants to stress-test a plan before building it, or when the user invokes any "grill" trigger phrase. It is specifically for interrogating a design's assumptions and decisions before implementation starts, not for reviewing code that already exists.

Questions are asked strictly one at a time, waiting for the user's answer before moving to the next - asking several questions at once is called out explicitly as "bewildering" and to be avoided. When a question could instead be answered by exploring the codebase directly, the skill explores the codebase rather than asking the user to explain something already discoverable in the code.

It has no dependencies of its own beyond the codebase it may explore in place of asking a question; related skills (Grill Me, Grill With Docs) reuse this same interview mechanism as their underlying engine.

Anyone about to commit to a plan or design who wants its assumptions pressure-tested one decision at a time, with a recommended answer offered for each open question, before writing any code.