bmad-edit-prd

To edit product requirements documents, a structured enhancement workflow applies BMAD-aligned improvements for clarity and completeness. It guides you through selecting the PRD file, gathering edit goals, and reviewing the format before restructuring the document for downstream engineering use.

The BMAD method for PRD editing transforms existing documents into a structured, standard format that is denser and easier to use. It applies strict step sequencing and controlled document writing to ensure product requirements are clear for downstream UX and architecture agents.

Yes, you can use a validation report to prioritize PRD fixes. The workflow auto-detects and optionally applies an existing validation-report file to target known issues, avoiding the repetition of previously identified errors during the document enhancement process.

To convert legacy product requirement documents, the workflow provides options to convert to BMAD format, apply targeted improvements, or do both. It routes non-standard PRDs through a conversion process while maintaining required YAML-frontmatter metadata.

Yes, editing product requirements requires YAML frontmatter metadata. The structured enhancement workflow mandates this metadata to properly process and write the controlled document output in the configured language.

Yes, you can customize the PRD editing workflow for specific needs. Optional workflow customization is supported via a configure file, allowing you to load persisted facts and tailor the document restructuring process to your project requirements.