requirements-validation-process

Validate software requirements through inspections, prototyping, and conceptual testing before baselining.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-validation-process-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-validation-process
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/requirements-validation-process
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-validation-process-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Requirements defects discovered during development or testing cost 10-100x more to fix than defects caught during requirements review. This Skill provides a structured validation process that catches ambiguity, incompleteness, inconsistency, and untestable requirements before they are baselined and handed to development. ## Core Features & Use Cases - Formal Inspection Workflow: Guides reviewer preparation, moderated review meetings, and defect classification by type and severity (Critical/Major/Minor). - Prototype Validation: Walks users through paper or low-fidelity prototypes to surface misunderstood workflows and missing requirements. - Conceptual Testing: Tests requirements against happy-path, error, edge-case, and performance scenarios before any code exists, plus acceptance criteria audits. - Use Case: Your SRS is drafted and the team is ready to build. Run this process to inspect all 35 requirements, prototype the key workflows, walk through test scenarios, resolve 38 defects, and formally baseline the document with stakeholder sign-off. ## Quick Start Validate my drafted SRS using formal inspection, prototype walkthroughs, and conceptual test scenarios, then produce a defect report and baseline decision.

Frequently Asked Questions about requirements-validation-process

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

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

Run a structured validation process: verify readiness (no open TBDs, unique IDs, traceability), conduct a formal inspection with prepared reviewers, prototype UI-heavy workflows with users, and walk through conceptual test scenarios. Resolve all critical defects before baselining.

What is the difference between requirements validation and verification?▼

Validation asks whether you are building the right thing, confirming requirements match stakeholder needs. Verification asks whether you built it right, confirming code matches requirements. This process focuses on validation before any code is written.

What is conceptual testing of requirements?▼

Conceptual testing writes 3-5 test scenarios per major requirement (happy path, error, edge case, performance) and asks what the system would do based solely on the written requirements. Unclear or unanswerable scenarios reveal ambiguity or gaps before coding begins.

When should I use a formal inspection versus an informal review?▼

Use formal Fagan-style inspections for critical or regulated systems where defect escape is costly. Use lighter peer reviews for lower-risk requirements. The process includes a readiness check and review-advisor step to select the appropriate formality level.

Why do requirements reviews fail to find defects?▼

Reviews fail when reviewers see requirements for the first time in the meeting, when defects are debated and fixed during the session instead of logged, or when no conceptual testing is performed. Require individual preparation and offline defect resolution.