Requirements Clarity

This stops you from building the wrong thing by forcing a structured conversation before any code gets written. When you get a vague request like "add login feature" or "implement payment," it runs a 100-point scoring rubric across functional clarity, technical specificity, implementation completeness, and business context. It asks focused questions in rounds of two or three until the spec hits 90 points, then generates a full PRD in your docs folder with acceptance criteria, execution phases, and risk assessment. The systematic approach works well for features over two days or anything involving cross-team work, though it can feel heavy for simple bug fixes where you already know exactly what to do.

skills.sh installs: 442
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill requirements-clarity --agent claude-code

Installs into .claude/skills of the current project.

Files

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:

Vague Feature Requests
- User says: "add login feature", "implement payment", "create dashboard"
- Missing: How, with what technology, what constraints?
Missing Technical Context
- No technology stack mentioned
- No integration points identified
- No performance/security constraints
Incomplete Specifications
- No acceptance criteria
- No success metrics
- No edge cases considered
- No error handling mentioned
Ambiguous Scope
- Unclear boundaries ("user management" - what exactly?)
- No distinction between MVP and future enhancements
- Missing "what's NOT included"