bmad-validate-prd

Validate PRDs against BMAD standards and generate structured findings.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Yukine5377/common --skill bmad-validate-prd-yukine5377
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-validate-prd
Source: https://github.com/Yukine5377/common/tree/main/.cursor/skills/bmad-validate-prd
Command: npx skills add https://github.com/Yukine5377/common --skill bmad-validate-prd-yukine5377

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

BMAD PRD validation ensures product requirements documents meet BMAD standards, improving quality, traceability, and downstream readiness.

Core Features & Use Cases

  • End-to-end BMAD PRD validation covering discovery, format detection, information density, product brief coverage, measurability, traceability, implementation leakage, domain compliance, project-type compliance, SMART quality, holistic quality, and completeness.
  • Automated validation report generation with structured findings and actionable gaps.
  • Optional branching paths for non-standard formats with parity assessment and human-in-the-loop decision points.

Quick Start

Provide the PRD file path and initiate the BMAD PRD validation workflow to produce a validation report.

Frequently Asked Questions about bmad-validate-prd

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

FAQPage Schema
How do I validate a PRD against BMAD standards?

Validating a PRD against BMAD standards involves running an automated workflow that checks discovery, format detection, density, measurability, traceability, and completeness, producing a structured report with actionable gaps.

What does BMAD PRD validation check for downstream readiness?

BMAD PRD validation checks downstream readiness by assessing information density, product brief coverage, implementation leakage, domain compliance, project-type compliance, and SMART quality to ensure the document meets strict artifact standards.

How do I identify gaps in my product requirements document?

Identifying gaps in your product requirements document requires running a validation workflow that analyzes traceability and completeness, generating structured findings with actionable recommendations to guide necessary revisions.

Can I validate non-standard PRD formats with this workflow?

You can validate non-standard PRD formats using optional branching paths that perform parity assessment and include human-in-the-loop decision points to accurately evaluate document readiness.

What should I do if my PRD fails BMAD compliance checks?

If your PRD fails BMAD compliance checks, review the generated validation report's structured findings and actionable recommendations to revise the document, improve traceability, and resolve implementation leakage.