Requirements Review Skill

Goal

Assess the quality of an existing requirements document (PRD, SRS, user stories, feature spec) using formal criteria. Identify gaps, inconsistencies, ambiguities, and missing stakeholder concerns. Produce a structured review report with actionable findings.

When to Use

• Scenario 2 (Review existing): Requirements already exist — PRD, SRS, user stories, feature descriptions, or any natural-language specification.
• Before architecture: Verify requirements are complete before designing a system.
• Before implementation: Gate check to catch gaps before code is written (cheaper to fix here).
• After requirements update: Re-review whenever requirements change significantly.

Step 1 — Load and Parse Requirements