domains / families / business / requirements-clarity

requirements-clarity

authentic

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

When to use

• Vague feature requests
• Missing technical context
• Incomplete specifications
• Ambiguous scope
• Features complex (>2 days)
• Cross-team coordination

When not to use

• Specific file paths mentioned
• Code snippets included
• Existing functions/classes referenced
• Bug fixes with clear reproduction steps

Skill page

Source