Agent skill · product strategy · davila7
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 coding.
Why this skill is useful
Provides a structured approach to transforming vague requirements into actionable PRDs, which the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
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 specifications Include measurable acceptance criteria Provide executable phases Enable direct implementation Clarification Process Step 1: Initial Requirement Analysis Input: User's requirement description Tasks: 1. Parse and understand core requirement 2. Generate feature name (kebab-case format) 3. Determine document version (default 1.0 unless user specifies otherwise) 4. Ensure ./docs/prds/ exists for PRD output 5. Perform initial clarity assessment (0-100) Assessment Rubric: Initial Response Format: Step 2: Gap Analysis Identify missing information across four dimensions: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/requirements-clarity