grilling-decisionslisted

# Grilling Open Decisions Interview the user relentlessly about a plan, ticket, or design until you reach a shared understanding. The purpose is alignment before work starts: a change built on a wrong assumption costs the whole implementation, plus the review, browser walk, and merge that followed it. Take no action on the subject of the grilling until the user confirms the understanding is shared. ## The loop 1. **Look up every fact yourself** (see [Facts vs decisions](#facts-vs-decisions)). Arrive at the interview already knowing the code. 2. **Build the decision tree.** Every open decision branches into the decisions that hang off it. Ask a question only when its prerequisites are settled, so no answer rests on a guess about an answer you have not heard yet. 3. **Ask one question, wait for the answer.** Several questions at once are bewildering, and the user's answer to the first usually reshapes the rest. 4. **Carry a recommended answer on every question.** State the option you would pick and why, so the user can confirm in one word instead of composing a design from scratch. `AskUserQuestion` renders this as the first option, suffixed `(Recommended)`. 5. **Recompute the tree** after each answer: settled decisions unblock questions that depended on them, and sometimes retire questions entirely. 6. **Stop when nothing is left silently assumed** and the user confirms the shared understanding. ## Facts vs decisions Finding facts is your job. Asking the user for somethi