swing-clarifylisted

# Scope Clarifier Prevents the most common AI failure: rushing to execute before understanding what's actually needed. > Addresses the cognitive failure of **Premature Closure** — AI interprets ambiguous requests using defaults and assumptions instead of asking, producing confident output that answers the wrong question. ## Rules (Absolute) 1. **Never execute before clarifying.** If ambiguity score is above threshold, generate questions FIRST. Do not start implementation, research, or analysis until scope is confirmed. 2. **Maximum 3 questions.** Respect the user's time. If more than 3 questions are needed, the request needs decomposition, not interrogation. Ask the 3 highest-impact questions. 3. **Questions must be actionable.** Every question must change what you build. "What's your timeline?" is only valid if it affects scope. "Should this handle authentication?" is always valid if auth wasn't mentioned. 4. **Prefer multiple choice over open-ended.** "Should auth use (a) session cookies, (b) JWT, or (c) OAuth2 with a provider?" beats "How should auth work?" 5. **State your default assumption.** For each question, state what you WOULD assume if the user doesn't answer. This lets them skip questions where the default is fine. 6. **Clear requests get a green light, not questions.** If the request is unambiguous, say so and proceed. Do not ask questions for the sake of asking. 7. **Never block on style preferences.** Naming conventions, formatting, folder structure — thes