bmad-validate-prd

To validate a PRD against project standards, use automated validation to check your draft document for missing sections, non-compliant terminology, and completeness before engineering review. It applies predefined checklists to ensure your product requirement documentation meets organizational requirements.

PRD validation is the automated process of checking product requirement documentation against predefined compliance guardrails. You need it before development begins to ensure technical specifications are complete, consistent, and meet quality control standards across your project.

Yes, you can use custom checklists to check product requirement documentation. The validation process integrates project-specific facts and regulatory constraints to ensure every document meets your organizational requirements and terminology standards.

To check a draft PRD for missing sections, provide the file path to initiate the automated validation workflow. It identifies missing sections and non-compliant terminology, ensuring the document is ready for engineering review.

Yes, PRD validation requires integration with the bmad-prd framework to enforce persistent facts and generate validation reports. This integration ensures context-aware compliance with project-specific facts and regulatory constraints.

Automated PRD compliance checking relies on predefined project standards and the bmad-prd framework integration. It cannot validate subjective quality or business logic outside established checklists, and requires project-specific facts to be configured for accurate regulatory constraint checks.