← ClaudeAtlas

requirements-claritylisted

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.
dills122/ai-central · ★ 0 · Web & Frontend · score 70
Install: claude install-skill dills122/ai-central
# Requirements Clarity Skill ## Description Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system. ## Instructions When invoked, detect vague requirements: 1. **Vague Feature Requests** - User says: "add login feature", "implement payment", "create dashboard" - Missing: How, with what technology, what constraints? 2. **Missing Technical Context** - No technology stack mentioned - No integration points identified - No performance/security constraints 3. **Incomplete Specifications** - No acceptance criteria - No success metrics - No edge cases considered - No error handling mentioned 4. **Ambiguous Scope** - Unclear boundaries ("user management" - what exactly?) - No distinction between MVP and future enhancements - Missing "what's NOT included" **Do NOT activate when**: - Specific file paths mentioned (e.g., "auth.go:45") - Code snippets included - Existing functions/classes referenced - Bug fixes with clear reproduction steps ## Core Principles 1. **Systematic Questioning** - Ask focused, specific questions - One category at a time (2-3 questions per round) - Build on previous answers - Avoid overwhelming users 2. **Quality-Driven Iteration** - Continuously assess clarity score (0-100) - Identify gaps systematically - Iterate until ≥ 90 points - Document all clarification rounds 3. **Actionable Output** - Generate concrete s