requirement-review — Claude Code skill: what it does, how to install
requirement-review reviews a requirements document before design begins: finds gaps, contradictions and vague wording, scores what it finds and writes a report.
MIT 129 installs ★ 18 updated 2026-01-23
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a claude-codeWhat requirement-review does
The skill runs a requirements document through six quality attributes: completeness, clarity, consistency, testability, traceability and feasibility. Each gets a score between 0 and 100%.
It starts by gathering the material: a BRD or SRS, user stories, non-functional constraints, the traceability matrix, existing acceptance criteria. Every requirement then goes past the checklists and lands in a report with an executive summary, findings sorted by severity, and action items carrying owners and due dates. Checklists, before/after examples and report templates sit in files under references/.
A document at 90% or above comes back approved. Scores of 60–74% mean substantial rework, and under 60% the skill tells you to rebuild the requirements from scratch. Findings point at requirement IDs, so number them first — otherwise the report has nothing to cite.
What it helps with
- Check a BRD for gaps and open TBDs before development starts
- Surface conflicting requirements and hand them to stakeholders
- Turn vague wording such as fast or easy into measurable criteria
- Score a user story backlog against INVEST and Given-When-Then
- Compare an SRS against the IEEE 830 structure
Example prompts for the agent
- Review
docs/BRD.mdfor completeness and clarity and give me the scored report. - Find conflicting requirements in the payments spec and list them by ID.
- Score this user story backlog against INVEST and flag missing acceptance criteria.
How to install requirement-review
1Skills CLI (Vercel)
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a claude-code2Manually: put the files in place
~/.claude/skills/requirement-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/requirement-review/
1Skills CLI (Vercel)
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a codex2Manually: put the files in place
.agents/skills/requirement-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a cursor2Manually: put the files in place
.cursor/skills/requirement-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install DauQuangThanh/hanoi-rainbow skills/requirement-review2Manually: put the files in place
.github/skills/requirement-review/SKILL.md1Skills CLI (Vercel)
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/DauQuangThanh/hanoi-rainbow --path skills/requirement-reviewManually: put the files in place
.devin/skills/requirement-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a opencodeClaude.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 requirement-review
How do I install requirement-review in Claude Code?
Run npx skills add DauQuangThanh/hanoi-rainbow --skill requirement-review -a claude-code. The skill file lands at ~/.claude/skills/requirement-review/SKILL.md.
What does requirement-review do?
It scores a requirements document on six quality attributes and returns a report with severity-ranked issues, action items with owners and due dates, and a final recommendation.
Which standards does it check against?
IEEE 830 for SRS documents, INVEST for user stories, ISO/IEC 25010 for the quality model. Regulated work also has HIPAA, PCI-DSS, SOC 2 and FDA sets.
Source text
SKILL.md · MIT
---
name: requirement-review
description: Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review reports with findings, gaps, conflicts, and improvement recommendations. Use when reviewing requirements documents (BRD, SRS, user stories), validating acceptance criteria, assessing requirements quality, identifying gaps and conflicts, or ensuring standards compliance (IEEE 830, INVEST criteria). Trigger when users mention "review requirements", "validate requirements", "check requirements quality", "find requirement issues", or "assess BRD/SRS quality".
---
# Requirement Review
Systematically review requirements to validate quality and identify issues before design and development begins. Ensure requirements are complete, clear, consistent, testable, and traceable.
## Review Workflow
## 1. Preparation
Gather all relevant documentation:
- Requirements documents (BRD, SRS, user stories)
- Non-functional requirements and constraints
- Requirements Traceability Matrix (if available)
- Project context (charter, goals)
- Existing acceptance criteria
### 2. Quality Assessment
Evaluate each requirement using **six quality attributes**:
1. **Completeness**: All needs captured, no missing details or TBDs, dependencies identified
2. **Clarity**: Unambiguous, specific, no vague terms ("user-friendly", "fast", "easy")
3. **Consistency**: No conflicts, consistent terminology and priorities
4. **Testability**: Verifiable with measurable acceptance criteria and clear pass/fail
5. **Traceability**: Links to business goals, design, and tests
6. **Feasibility**: Technically achievable within constraints (budget, timeline, capability)
> **See [quality-checklists.md](references/quality-checklists.md)** for detailed assessment criteria and document-specific checklists
### 3. Issue Identification
Identify common requirement problems:
**Ambiguous**: "system shall be fast" → Specify measurable criteria: "< 2s response for 95% of requests"
**Untestable**: "system shall be secure" → Define specific controls: password complexity, encryption standards, audit logging
**Incomplete**: "system shall send notifications" → Specify channel, timing, content, recipients
**Conflicting**: REQ-012 "phone required" vs REQ-089 "phone optional" → Flag for stakeholder resolution
> **See [examples.md](references/examples.md)** for extensive before/after examples
### 4. Quality Scoring
Calculate scores for each quality attribute (0-100%):
- **90-100%**: Excellent - minimal issues
- **75-89%**: Good - minor improvements needed
- **60-74%**: Fair - notable gaps exist
- **Below 60%**: Poor - major rework required
**Overall Quality** = Average of all six attributes
**Target**: ≥ 90% for production-readiness
### 5. Report Generation
Create structured review report with:
**Executive Summary**: Quality rating, recommendation, key strengths (2-3), critical issues (2-3), top actions
**Detailed Findings**: Quality scores, issues by severity (Critical/Major/Minor), specific examples with requirement IDs
**Action Items**: Prioritized list with owners, due dates, effort estimates, approval conditions
> **See [report-templates.md](references/report-templates.md)** for complete report structure and templates
### 6. Recommendations
Provide clear decision:
- **Approve**: Requirements ≥ 90% quality threshold
- **Approve with Conditions**: Critical issues must be resolved before design
- **Major Revision**: 60-74% quality - substantial rework required
- **Reject**: < 60% quality or fundamental issues - complete redesign needed
## Document-Specific Focus
### Business Requirements Documents (BRD)
Focus on business objectives, stakeholder needs, scope definition, business case, constraints
### Software Requirements Specifications (SRS)
Focus on functional requirements, non-functional requirements (performance, security, scalability), system behaviors, integration points, IEEE 830 compliance
### User Story Backlogs
Focus on INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable), acceptance criteria format (Given-When-Then), story format, prioritization
> **See [quality-checklists.md](references/quality-checklists.md)** for document-specific assessment criteria
## Severity Definitions
- **Critical**: Blocks progress, must fix immediately (security gaps, fundamental conflicts, missing scope)
- **Major**: Significant quality impact, should fix before approval (ambiguous criteria, missing acceptance criteria)
- **Minor**: Quality improvements, nice to have (formatting, examples, enhancements)
## Common Anti-Patterns to Flag
- **Gold Plating**: Adding unrequested features
- **Solution-Focused**: Specifying "how" instead of "what" (requirements should be technology-agnostic)
- **Scope Creep**: Accepting changes without change control
- **Analysis Paralysis**: Over-perfecting requirements indefinitely
- **Weak Acceptance Criteria**: Vague or missing test conditions
- **No Traceability**: Requirements disconnected from business goals
## Vague Terms to Replace
Always replace with measurable criteria:
- "user-friendly", "intuitive", "easy" → Define usability metrics
- "fast", "quick", "responsive" → Specify response time targets
- "secure" → Define specific security controls
- "scalable" → Define capacity and load targets
- "reliable" → Define uptime percentage and recovery time
## Standards Compliance
- **IEEE 830**: SRS structure and content standards
- **INVEST**: User story quality criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable)
- **ISO/IEC 25010**: Systems and software quality models
- **Industry-Specific**: HIPAA (healthcare), PCI-DSS (payments), SOC 2 (SaaS), FDA (medical devices)
> **See [quality-checklists.md](references/quality-checklists.md)** for standards compliance details
## Report Format
Generate review reports in this structure:
1. **Executive Summary** (1 page): Overall assessment, key findings, recommendation
2. **Quality Metrics** (0.5 page): Scores by attribute with targets
3. **Detailed Findings** (2-5 pages): Issues grouped by attribute with examples and recommendations
4. **Action Items** (1 page): Prioritized list with owners and due dates
5. **Approval Decision** (0.5 page): Recommendation with rationale and next steps
Keep reports factual, specific, and actionable. Always cite specific requirement IDs when identifying issues.
> **See [report-templates.md](references/report-templates.md)** for complete report templates
© DauQuangThanh · MIT · DauQuangThanh/hanoi-rainbow