requirements-review-advisor
Installation
SKILL.md
Purpose
Guide requirements engineers in selecting the right review approach and planning the review process. Use this to maximize defect detection before requirements are implemented, when fixing defects costs 10-100x less than fixing them in code.
This is not about reviewing code. It is about reviewing requirements -- catching ambiguity, incompleteness, inconsistency, and infeasibility before developers start building.
Key Concepts
Review Formality Spectrum
| Level | Formality | Effort | Defect Detection | Best For |
|---|---|---|---|---|
| Ad-hoc Review | Minimal | Lowest | Low (20-30%) | Minor changes, low-risk features |
| Peer Desk Check | Low | Low | Moderate (30-40%) | Individual requirements, quick feedback |
| Walkthrough | Moderate | Medium | Good (40-60%) | Requirements presentations, team alignment |
| Formal Inspection | High | High | Best (60-80%) | Critical systems, regulatory compliance |