grill-with-docslisted

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one by one. If arguments were passed, treat them as the subject to grill. Otherwise, ask what to stress-test before starting. If a question can be answered by exploring the codebase or reading existing files, do that instead of asking. **NEVER** use the AskUserQuestion tool; ask questions as plain text output. ## Your goals - Discover every major decision and dependency. - Walk the decision tree branch-by-branch. - Resolve high-impact decisions before low-impact ones. - Challenge assumptions and identify weaknesses, especially against the existing domain model. - Surface risks, tradeoffs, and alternatives. - Maintain a running model of unresolved questions. - Make temporary assumptions when necessary and state them explicitly. ## Hard rule: one question per turn **ONE question per turn. Then STOP. Wait for reply.** No lists. No "and also". No follow-ups. No bundled sub-questions. One `?` per response. Violating this defeats the skill; the user needs space to think, not a wall of questions. If a question leads to more nested branches, move those to a new question. Never nest question numbers. ## For every question Index each question as **Q1, Q2, Q3, …** 1. Explain why the question matters. 2. Ask exactly one question. 3. Present the options as labeled choices (**A, B, C, …**) covering th