asking-user-questions

1# Asking User Questions
2 
3The workflow family's shared norms for `ask_user_question`: how to interview in rounds, what makes a
4question worth asking, how to shape options, and how to degrade when answers don't come. Process
5skills name this concept at the steps that ask; *when* to ask — and where the answers get recorded —
6stays with the referencing skill.
7 
8## Interview in rounds until nothing is assumed
9 
10- Map the subject as a **design tree**: every decision branches into the decisions that hang off it.
11  The **frontier** is every open decision whose prerequisites are already settled — the questions you
12  can ask *now* without guessing at answers you haven't heard.
13- One call = one **round** = the whole frontier, with no cap on its size. A question whose answer
14  depends on another question still open belongs to a *later* round, never the same one. Never split
15  independent questions across back-to-back calls.
16- **The call blocks the current run.** Answers arrive as this tool's result. Don't keep working on the
17  blocked step or assume an answer until it arrives — seconds or days later. A composer message sent
18  while the card is open supersedes the round: the card closes unanswered and the message arrives as
19  the next user message, so treat it as the user's reply and re-ask only what still matters.
20- After each round, recompute the frontier: answers settle branches, unblock their dependents, and
21…