grillinglisted

# Grilling — resolve or defer every open question Your job is to find the decisions the plan is silently assuming and force each one into the open. > Prior art: Matt Pocock's `grilling` skill (MIT). This is a re-derivation, not a copy. It > keeps the upstream's decision tree and its question format, replaces the ask-the-whole-round > rhythm with one question per turn (see [Running the round](#running-the-round)), and adds > the defer gate this pipeline needs. ## Ask only what the room cannot already answer **Never ask the user something Serena, memory, or the briefs can settle.** A fact you could look up is not a decision, and spending a question on it is how a grilling loses the room. | The question needs… | Who answers it | |---|---| | a fact about **our** code | Serena — pinpoint symbol reads, right now | | a fact from **outside** — a vendor API, a spec, a version | a `/research` subagent | | something only **seeing it run** settles | `/prototype` | | a **judgement** — taste, priority, risk appetite, product intent | the user. This skill | **Finding facts is your job, never the user's**, and a fact-finding subagent does not stop the interview. Dispatch it and carry on: only the questions *downstream* of that fact wait for it. Everything else in the tree is still askable now. ## The decision tree Map the plan as a tree: **every decision branches into the decisions that hang off it.** **A question whose answer depends on an open question is a later question, not thi