cast-interactive-questionslisted

# Interactive Question Protocol When you need user input during an interactive workflow, ALWAYS use the **AskUserQuestion tool**. Never ask questions as plain conversational text -- the tool provides structured rendering with options, recommendations, and clear formatting that plain text cannot match. ## Rules ### 1. One question at a time Ask the single most important question, wait for the answer, then proceed or ask the next. **NEVER batch multiple questions or issues into one AskUserQuestion call.** Even if you have 5 issues to raise, present them one by one. This lets the user focus, give thoughtful answers, and change direction early without wading through a wall of text. ### 2. Structured options When there are discrete choices, present them as **lettered options** (A, B, C). Include "do nothing" or "defer" as an option where reasonable. ### 3. Recommendation first Lead with your recommended option marked **(Recommended)** and explain **WHY** with grounded reasoning. "Grounded" means you cite evidence from artifacts you've actually read -- exploration results, requirements, code patterns, spec behavior, task history -- not generic advice. ### 4. Grounded reasoning per option Each option gets a 1-2 sentence rationale based on what you've observed. Bad: "This is simpler." Good: "The exploration playbook rated this approach 9/10 impact and the codebase already has a `ServiceBase` pattern at `services/base.py` that this would extend naturally." ### 5. Sequential