ask-userlisted

# Ask User Thin helper that codifies how to ask the user questions during a workflow. Other skills (planning, research, brainstorming, implementing) reference this skill instead of duplicating AskUserQuestion conventions. ## Core Rule **Use the AskUserQuestion tool — never as plain-text bullets in chat.** Asking in chat looks like a request for free-form prose; AskUserQuestion gives the user one click per decision and the answer is structured. Always prefer the tool. ## When to Use - Clarifying ambiguous user input - Choosing between viable design options - Confirming a non-trivial assumption before acting on it - Approving a phase boundary, plan structure, or destructive action - Capturing a workflow preference (e.g., commit-per-phase) ## When NOT to Use - Rhetorical questions or thinking-out-loud - Asking permission for trivial, reversible actions (just do them) - "Is the plan ready?" / "Should I proceed?" — those are not decisions, they're checkpoints; just present the artifact and stop ## Conventions ### Question shape - **One sentence**, ends with `?` - Include enough context that the user doesn't need to scroll back - Don't reference invisible artifacts ("does the plan look good?" — they may not see it yet) ### Options - 2–4 mutually exclusive choices - Each option: 1–5 word **label**, plus a one-sentence **description** explaining the trade-off or implication - If you have a recommendation, put it **first** and append `(Recommended)` to the label - Never i