bmad-edit-prd

Forwards legacy PRD update invocations to the consolidated bmad-prd workflow.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-edit-prd-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-edit-prd
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-edit-prd-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing projects and customization files that still reference the old bmad-edit-prd skill would break after it was merged into bmad-prd; this compatibility shim keeps those invocations working while guiding users to migrate. ## Core Features & Use Cases - Backward Compatibility: Resolves legacy _bmad/custom/bmad-edit-prd.toml overrides (activation steps, persistent facts, on_complete) and forwards them to bmad-prd. - Deprecation Notice: Emits a localized warning explaining the consolidation and how to migrate customization files to bmad-prd.toml. - Intent Forwarding: Invokes bmad-prd with update intent pre-set, skipping its intent detection step. - Use Case: A team with an existing bmad-edit-prd.toml customization runs the old skill name; the shim loads their overrides, warns about deprecation, and hands off to bmad-prd to update the target PRD. ## Quick Start Invoke bmad-edit-prd with the path to the PRD you want to update and describe the change you need.

Frequently Asked Questions about bmad-edit-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update an existing PRD with BMAD?

Invoke bmad-prd directly with the target PRD path and your change description; it detects update intent automatically. The legacy bmad-edit-prd name still works but simply forwards to bmad-prd with update intent pre-set.

Is bmad-edit-prd deprecated?

Yes, bmad-edit-prd is deprecated and retained only as a compatibility shim. It emits a deprecation notice and forwards all work to bmad-prd, and it will be removed in a future release.

Will my bmad-edit-prd.toml customization still work?

Yes, legacy fields like activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete are resolved from bmad-edit-prd.toml and passed to bmad-prd. Migrating the file to bmad-prd.toml unlocks additional customization fields.

How do I migrate from bmad-edit-prd to bmad-prd?

Rename your `_bmad/custom/bmad-edit-prd.toml` file to `_bmad/custom/bmad-prd.toml` and invoke bmad-prd directly. Existing field values are respected, and you gain access to new options like prd_template, validation_checklist_template, and prd_output_path.

Why does bmad-edit-prd show a deprecation notice?

The notice appears because the skill was consolidated into bmad-prd and only exists as a forwarding shim. Migrating your customization file and calling bmad-prd directly silences the notice.