requirements-clarity — Claude Code skill: what it does & setup
Clarifies fuzzy feature descriptions through targeted questions before coding starts. It scores requirements on a 100-point scale and writes a finished PRD file.
npx claude-code-templates@latest --skill productivity/requirements-clarityWhat requirements-clarity does
The skill catches abstract prompts like "build dashboard" or "add payments". Rather than letting the model draft arbitrary code, it grades the task across four areas: functional scope (up to 30 points), technical constraints (25), edge cases with error paths (25), and business context (20).
Interviews proceed in short cycles of two or three focused questions per turn. The assistant updates the clarity score after each reply. Once the total reaches 90 points, it writes the specification directly to ./docs/prds/{feature_name}-v{version}-prd.md with acceptance criteria, architecture choices, and boundaries.
Targeted tasks will not trigger this flow: prompts referencing specific file paths like auth.go:45, inline code samples, or explicit bug reproduction steps bypass clarification entirely.
What it helps with
- turn vague task prompts into a structured PRD document
- uncover edge cases and validation rules before writing code
- establish measurable acceptance criteria and architecture boundaries
- filter out unnecessary work using YAGNI and KISS principles
Example prompts for the agent
- I want to add user authentication to the project, help me write the PRD
- We need a dashboard for analytics, ask the necessary questions to clarify scope
- Help me specify requirements and technical constraints for payment integration
How to install requirements-clarity
1claude-code-templates
npx claude-code-templates@latest --skill productivity/requirements-clarity2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill requirements-clarity -a claude-code3Manually: put the files in place
~/.claude/skills/requirements-clarity/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/requirements-clarity/
Manually: put the files in place
.agents/skills/requirements-clarity/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/requirements-clarity/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates requirements-clarity2Manually: put the files in place
.github/skills/requirements-clarity/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/productivity/requirements-clarityManually: put the files in place
.devin/skills/requirements-clarity/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about requirements-clarity
How do I install requirements-clarity in Claude Code?
Run npx claude-code-templates@latest --skill productivity/requirements-clarity or install it with npx skills add davila7/claude-code-templates --skill requirements-clarity -a claude-code.
What does requirements-clarity do?
It conducts an interactive inquiry using a 100-point grading system and generates a PRD file in ./docs/prds/ once clarity hits 90 points.
When does requirements-clarity skip clarification?
It stays inactive if you provide code snippets, direct file references like auth.go:45, existing functions, or reproducible bug reports.