bmad-edit-prd

To edit an existing PRD to align with BMAD standards, provide the PRD path and explicit edit goals. The workflow routes through discovery, deep review, and change planning before applying any edits to ensure structured refinement.

A BMAD change plan is a required approval step before applying modifications to a PRD. You need one whenever editing a BMAD Standard, BMAD Variant, or Legacy PRD to ensure all changes are reviewed and validated before implementation.

Yes, this workflow supports restructuring Legacy PRDs into BMAD formats. It routes through discovery to determine the current format and validation needs, then guides deep review and editing to align the document with BMAD standards.

A validation report is optional but recommended for quality assurance during PRD editing. You can provide a validation report path during the discovery phase to integrate validation checks into the change planning and editing steps.

The best way to plan changes for a BMAD Variant PRD is to provide explicit edit goals upfront. The workflow captures your intent during discovery, performs a deep review, and generates an approved change plan before any edits are applied.

Explicit edit goals are required because they drive the discovery and routing logic. Without clear goals, the workflow cannot determine the BMAD format type, validation needs, or generate an appropriate change plan for the PRD editing session.