ask-me-questionslisted

# Ask Me Questions Understand before you act. Ask targeted questions using `AskUserQuestion` in focused multi-round conversations before proceeding with any task. ## Rules 1. **Never jump to solutions.** When this skill triggers, questioning comes FIRST. 2. **Never ask what you can verify.** Read the code, run the command, check the docs first. Ask only about intent, preferences, priorities, and trade-offs the code can't reveal. 3. **Use `AskUserQuestion` exclusively** — not inline text questions. 4. **Max 4 questions per round** (tool constraint). Make each one count. 5. **Adapt rounds to complexity:** - Simple (single-file change, config tweak): 1 round (2-4 questions) - Medium (feature, multi-file change): 2 rounds (4-8 questions) - Complex (architecture, new system): 2-3 rounds (6-12 questions) 6. **Stop questioning when:** you have enough clarity to act confidently. Don't over-ask. 7. **Unattended runs don't block.** If running autonomously (background, cron, headless) where no one can answer, skip questioning: state your assumptions explicitly and proceed. ## Questioning Workflow ### Round 1: Scope & Intent Establish what the user actually wants and why. These questions cut through ambiguity fast. Focus areas: - **What:** What specific outcome do they want? What does "done" look like? - **Why:** What problem does this solve? What triggered this request? - **Constraints:** Are there hard requirements (tech stack, timeline, compatibility)? - **