--- name: grilling description: >- Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. disable-model-invocation: false metadata: credit: "Adapted from Matt Pocock's grilling skill, github.com/mattpocock/skills (MIT, (c) 2026 Matt Pocock)" --- Interview the user relentlessly until you reach a shared understanding. Map this as a **design tree**: every decision branches into the decisions that hang off it. Work the tree in **rounds**. The **frontier** is every decision whose prerequisites are already settled: the questions you can ask _now_ without guessing at answers you haven't heard yet. Ask the whole frontier in one round: number each question and give your recommended answer. Then wait for the user's answers before the next round. Format a round like so: ``` ❓ **Q1** - ****: ➡️ --- ❓ **Q2** - ****: ➡️ ``` Word each question so "yes" accepts your recommended answer. In each question body, say why the decision matters, and give the trade-offs of each choice. Clearly distinguish descriptions of how the system currently works from proposals about how it should work. Challenge as you go: requirements that look unnecessary or overcomplicated, implied scope, and contradictions with earlier answers or with the code. Each round the user answers reshapes the tree: settled decisions push the frontier outward and unblock questions that depended on them. Recompute the frontier and ask the next round. A question whose answer depends on another question still open in this round belongs to a _later_ round, not this one. Finding _facts_ is your job, never the user's. When a frontier question needs a fact from the environment (filesystem, tools, etc.), dispatch a `cheap` sub-agent with a fresh context window to find it; don't ask the user for anything you could look up yourself. Don't block on it: a running exploration is an unsettled prerequisite, so only the questions downstream of it wait for the sub-agent to report; ask the rest of the frontier now. The _decisions_ are the user's: put each to them and wait. ## Terms and lasting decisions When a term is fuzzy, overloaded, or conflicts with the project's glossary, or a decision is hard to reverse and would surprise a future reader, use the `/domain-modeling` skill. Everything else stays in the conversation. ## Finishing The session is done when the frontier is empty: every branch of the design tree visited, nothing left silently assumed. Eliminate "intent debt": the implicit goals, constraints and rationale that may exist in outputs that the user didn't write. Do not act on it until the user confirms you have reached a shared understanding.