requirements-clarity

1# Requirements Clarity Skill
2 
3## Description
4 
5Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system.
6 
7 
8## Instructions
9 
10When invoked, detect vague requirements:
11 
121. **Vague Feature Requests**
13   - User says: "add login feature", "implement payment", "create dashboard"
14   - Missing: How, with what technology, what constraints?
15 
162. **Missing Technical Context**
17   - No technology stack mentioned
18   - No integration points identified
19   - No performance/security constraints
20 
213. **Incomplete Specifications**
22   - No acceptance criteria
23   - No success metrics
24   - No edge cases considered
25   - No error handling mentioned
26 
274. **Ambiguous Scope**
28   - Unclear boundaries ("user management" - what exactly?)
29   - No distinction between MVP and future enhancements
30   - Missing "what's NOT included"
31 
32**Do NOT activate when**:
33- Specific file paths mentioned (e.g., "auth.go:45")
34- Code snippets included
35- Existing functions/classes referenced
36- Bug fixes with clear reproduction steps
37 
38## Core Principles
39 
401. **Systematic Questioning**
41   - Ask focused, specific questions
42   - One category at a time (2-3 questions per round)
43   - Build on previous answers
44   - Avoid overwhelming users
45 
462. **Quality-Driven Iteration**
47   - Continuously assess clarity score (0-100)
48   - Identify gaps systematically
49   - Iterate until ≥ 90 points
50   - Document all clarification rounds
51 
523. **Actionable Output**
53…