| name | requirement-clarification |
| description | Guidelines for asking clarifying questions when requirements are ambiguous. Use when scope is unclear, multiple approaches exist, or critical details are missing. |
Requirement Clarification
Quick Start
- Identify ambiguity -> Formulate specific questions -> Ask before implementing
- Ask about scope, edge cases, and trade-offs when unclear
- Propose options with trade-offs when multiple approaches exist
- Never assume - verify critical decisions with user
Key Principles
- Ask early: Clarify before writing code, not after
- Be specific: Ask targeted questions, not vague ones
- Offer options: Present 2-3 approaches with trade-offs
- Batch questions: Group related questions together
- Know when NOT to ask: Skip for trivial/obvious decisions
When to Ask
- Multiple valid implementations exist
- Business logic implications unclear
- Scope boundaries undefined
- Breaking changes possible
- Security/performance trade-offs involved
References
See rules.md for question templates and anti-patterns.
