vaguelisted

# Vague: Requirement Clarification Transform vague or ambiguous requirements into precise, actionable specifications through hypothesis-driven questioning. **ALWAYS use the AskUserQuestion tool** — never ask clarifying questions in plain text. ## 사용 시나리오 - Ambiguous feature requests ("add a login feature") - Incomplete bug reports ("the export is broken") - Underspecified tasks ("make the app faster") For strategy/planning blind spot analysis, use the **unknown** skill. For pointed pre-implementation planning questions on a plan you already have, use **grill-me**. For requirements + design + verification + execution, use **ouroboros**. ## Core Principle: Hypotheses as Options Present plausible interpretations as options instead of asking open questions. Each option is a testable hypothesis about what the user actually means. ``` BAD: "What kind of login do you want?" ← open question, high cognitive load GOOD: "OAuth / Email+Password / SSO / Magic link" ← pick one, lower load ``` ## Protocol ### Phase 1: Capture and Diagnose Record the original requirement verbatim. Identify ambiguities: - What is unclear or underspecified? - What assumptions would need to be made? - What decisions are left to interpretation? ### Phase 2: Iterative Clarification Use AskUserQuestion to resolve ambiguities. **Batch up to 4 related questions per call.** Each option is a hypothesis about what the user means. **Cap: 5-8 total questions.** Stop when all critical ambiguities a