bmad-edit-prd

To update legacy product requirement documents safely, you can use a compatibility shim that forwards existing update requests to a unified backend while preserving your deprecated configuration parameters and enforcing modern validation protocols.

A PRD migration shim is a compatibility layer needed when transitioning automated product management workflows to a newer system architecture without immediately rewriting existing configuration files or breaking established update triggers.

No, you do not need to manually migrate TOML configuration files beforehand, because the skill automatically maps deprecated customization settings from legacy files to current architectural standards during the document update process.

To apply changes to a product specification, invoke the skill followed by the file path to your PRD and the specific modifications you wish to apply, and the unified backend will process the update automatically.

Yes, existing automated triggers will continue to work because the compatibility layer ensures backward compatibility for automated triggers while routing update requests through the modern product management system.

The primary limitation is that this approach is a transitional bridge; while it enforces modern validation and reporting protocols, it relies on mapping deprecated parameters rather than fully migrating your configuration to the new architectural standards.