What problem does it solve? Requirements defects discovered late in development cost 10-100x more to fix than those caught during validation. This Skill guides the formal validation step of the Requirements Management cycle, ensuring specifications are both internally correct (verification) and actually solve stakeholder needs (validation) before baseline approval. ## Core Features & Use Cases - Verification vs Validation Distinction: Separates quality-standard checks (IEEE 830 checklist) from stakeholder need confirmation, preventing approval of well-written but wrong requirements. - Multiple Validation Techniques: Supports informal walkthroughs, formal Fagan inspections with 6-phase protocol and defect taxonomy, prototype validation, and UAT sessions selected by project context. - Sign-off Matrix & Flow Decision: Produces a formal approval matrix per stakeholder role and a documented decision to advance to requirements management or return to analysis with specific defects. - Use Case: After completing a requirements specification baseline, run this Skill to conduct a Fagan inspection, log defects by type (Missing, Wrong, Ambiguous, Inconsistent), obtain sponsor and user sign-off, and generate the rm-validation.md report. ## Quick Start Ask the AI to validate the requirements specification in the current work package and produce a validation report with defect log and stakeholder sign-off matrix.
