bmad-req-validator

Classify functional requirements and recommend analysis methodologies to detect gaps.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill bmad-req-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-req-validator
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/bmad-req-validator
Command: npx skills add https://github.com/russosalv/NONoise --skill bmad-req-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many functional requirements and user stories are vague, untestable, or missing critical context, causing rework, missed assumptions, and implementation risk. This Skill systematically classifies a requirement, recommends the most appropriate analysis methodologies, runs only the selected checks, deduplicates overlapping gaps, and converts each confirmed gap into a single, business-friendly challenge question for an analyst to answer.

Core Features & Use Cases

  • Classification: Tag requirements by type, abstraction level, criticality and context to drive the right validation path.
  • Methodology recommendation: Propose a focused 2–5 methodology subset (INVEST, SMART, EARS, MoSCoW, WOTIF, IEEE 830, FMEA-Lite, SWOT, ATAM-Lite) and wait for analyst confirmation before execution.
  • Selective validation & aggregation: Execute chosen methods, flag PASS/WARN/FAIL, deduplicate overlapping gaps, rank by severity, and produce a validation report stored alongside the original doc.
  • Challenge questions: Generate open, non-technical questions for each FAIL/WARN gap to elicit precise answers from stakeholders.
  • Use Case: Analyst-run formal validation of a draft PRD user story or NFR prior to architecture handoff or a tender response.

Quick Start

Run bmad-req-validator on the requirement text to classify it, propose methodologies, and generate a validation report with aggregated gaps and challenge questions.

Frequently Asked Questions about bmad-req-validator

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

FAQPage Schema
How do I validate functional requirements in a draft PRD for gaps and untestable criteria?

To validate functional requirements, the Skill classifies their type and applies selected analysis methodologies like INVEST or EARS to detect gaps, rank them by severity, and generate challenge questions without modifying the original text.

What is the best way to generate challenge questions for vague user stories before architecture handoff?

Generating challenge questions involves running selective validation methods on user stories, flagging WARN or FAIL gaps, and converting each confirmed gap into a business-friendly question for analysts to elicit precise answers from stakeholders.

How do I run a gap analysis on technical requirements and NFRs?

Running a gap analysis on technical requirements and NFRs requires classifying the requirement, selecting 2-5 appropriate methodologies such as IEEE 830 or FMEA-Lite, and aggregating the detected weaknesses into a ranked validation report.

Can I use SMART and MoSCoW methodologies together to check draft requirements?

You can use SMART and MoSCoW methodologies together during validation; the process proposes a focused subset of 2-5 methodologies and waits for analyst confirmation before executing the checks and deduplicating overlapping gaps.

Does validating requirements modify the original PRD document?

Validating requirements does not modify the original PRD document; instead, it produces classification blocks, per-method scores, and a sibling validation report stored alongside the original doc to preserve source integrity.