Requirements Clarity
원문: requirements-clarity
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 c
무엇을 하나요
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?) …
실행 시 본인 API 키(BYOK)로 동작하며, 모델 비용은 사용자 계정에서 직접 결제됩니다.