bmad-validate-prd

PRD validation systematically checks an existing document against BMAD standards by verifying format, information density, coverage, measurability, traceability, implementation leakage, domain compliance, and SMART quality to catch missing structure and weak requirements before downstream planning begins.

To validate a PRD for traceability and coverage, provide the document path and any referenced input files. The validation process identifies missing sections, orphan requirements, and quality issues, then records findings in a stepwise assessment report with actionable compliance status.

Yes, validating a PRD requires the document frontmatter and any referenced input documents to produce a complete validation report. These inputs allow the systematic review to accurately check implementation leakage, domain compliance, and SMART quality.

You should run a SMART quality and compliance check on your PRD before UX, architecture, or delivery work begins. Validating the document at this stage prevents traceability gaps and weak requirements from impacting downstream development.

The best way to find orphan requirements is to validate the PRD against BMAD standards using its frontmatter and referenced inputs. This gap analysis identifies missing sections and quality issues, then records them in an actionable compliance report.