requirements-clarity

Topics in the source

• Requirements Clarity Skill
• Description
• Instructions
• Core Principles
• Clarification Process
• Step 1: Initial Requirement Analysis
• Step 2: Gap Analysis
• Step 3: Interactive Clarification

Automatically transforms vague requirements into actionable PRDs through systematic clarification with a 100-point scoring system. 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 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

This is an excerpt. Refer to the complete source and its current requirements.