rm-validation

Validates requirements specifications through inspection, stakeholder review, and formal sign-off.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/NestorMonroy/thyrox --skill rm-validation-nestormonroy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rm-validation
Source: https://github.com/NestorMonroy/thyrox/tree/main/.claude/skills/rm-validation
Command: npx skills add https://github.com/NestorMonroy/thyrox --skill rm-validation-nestormonroy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

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 sign-off. ## 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 defect taxonomy (Missing/Wrong/Extra/Ambiguous/Inconsistent), prototype validation, and UAT sessions. - Sign-off Matrix & Flow Decision: Produces a formal approval matrix per stakeholder 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 inspect 40 checklist items per requirement type, log defects by severity, hold a stakeholder review session, and produce a signed validation report. ## Quick Start Ask the AI to validate the requirements specification in your work package and produce a validation report with defect log and stakeholder sign-off matrix.

Frequently Asked Questions about rm-validation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate requirements before development starts?▼

Run a structured validation pass: verify each requirement against a quality checklist (complete, unambiguous, testable, traceable), then confirm with stakeholders that requirements solve their real needs. Document defects in a log and obtain formal sign-off before baselining.

What is the difference between requirements verification and validation?▼

Verification checks whether a requirement meets quality standards (well-written, testable, consistent). Validation confirms the requirement solves the stakeholder's actual business need. A requirement can pass verification yet fail validation, so both must be executed.

What is a Fagan inspection for requirements review?▼

A Fagan inspection is a formal six-step review process: planning, overview, individual preparation, inspection meeting, rework, and follow-up. It uses defined roles (moderator, author, reviewers, scribe) and detects 70-85% of defects, roughly twice the rate of informal walkthroughs.

When should requirements validation return to analysis?▼

Return to analysis when defects of type Wrong or Inconsistent are found, when Must Have requirements lack verifiable acceptance criteria, or when a key stakeholder rejects sign-off with justification. Document exactly which defects require re-analysis rather than repeating the whole analysis.

What are the limitations of formal requirements sign-off?▼

Sign-off only confirms stakeholders agreed with what they read; it does not guarantee correctness. Fagan inspections also require a trained moderator, and UAT may reveal needs never articulated during elicitation, requiring additional elicitation iterations.