Vague: Requirement Clarification

Transform vague requirements into precise, actionable specifications through hypothesis-driven questioning.

When to Use

• 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 unknown. For content-vs-form reframing, use metamedium.

Core Principle: Hypotheses as Options

Use AskUserQuestion for clarification. Do not ask open-ended free-text questions when options can represent plausible hypotheses.

• Bad: What kind of login do you want?
• Good: OAuth / Email+Password / SSO / Magic link