grilllisted

# /grill — Requirement Interrogation Structured process for validating requirements before implementation. Ambiguous requirements are the #1 source of wasted tokens — a swarm that builds the wrong thing costs 10x more than grilling first. ## Mode **Always run grill as a plan with Q&A.** Before starting, enter plan mode (`EnterPlanMode`). Grill is a structured conversation — the agent asks questions, the human answers, and each step builds on prior answers. No file writes, no code edits, no tool calls beyond search/read. **Format:** For each step, the agent: 1. States its analysis or best-guess interpretation 2. Asks **one sharp question** via `AskUserQuestion` with yes/no or 2-4 numbered options 3. Waits for the human's response before advancing No diagrams. PDS runs in a terminal where graphical blocks render as unreadable text — use prose lists, file paths, and concrete counts instead. Do not skip steps or combine them. Do not proceed past a step without the human's input — the structured Q&A prevents premature convergence and surfaces assumptions early. ## Question Discipline Five rules govern every question in the protocol: 1. **One sharpest question per turn.** Each step may surface multiple uncertainties — pick the one whose answer most constrains the next step, ask that, queue the rest. Never stack 3+ questions in a single turn; the human can only hold one in working memory. 2. **No hedge trailers.** Do not end questions with "or am I missing something?", "doe