bmad-edit-prd

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-edit-prd-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-edit-prd
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-edit-prd-tuanpa-nhg-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing projects and customization files that still reference the retired bmad-edit-prd skill would break after it was merged into bmad-prd. This compatibility shim keeps those legacy invocations working while guiding users toward the new consolidated workflow. ## 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 notice explaining the migration path to bmad-prd.toml and the new customization fields available. - 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 file invokes the old skill name; the shim loads their overrides, warns about deprecation, and runs the PRD update through bmad-prd without losing their settings. ## Quick Start Invoke bmad-edit-prd with the target PRD path and the change you want, and it will forward the request to bmad-prd with update intent.

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 the BMad method?

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

What happened to the bmad-edit-prd skill?

It was consolidated into bmad-prd and retained only as a thin compatibility shim. It resolves legacy customization overrides, shows a deprecation notice, and delegates all actual work to bmad-prd.

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

Yes, the shim resolves legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) from bmad-edit-prd.toml and passes them to bmad-prd. Migrating to bmad-prd.toml unlocks additional fields like prd_template and validation_checklist_template.

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

Rename or move your overrides from _bmad/custom/bmad-edit-prd.toml to _bmad/custom/bmad-prd.toml and invoke bmad-prd directly. Existing fields remain respected, and you gain access to new options like doc_standards, finalize_reviewers, and prd_output_path.

Why am I seeing a deprecation notice when editing a PRD?

The notice appears because the deprecated bmad-edit-prd shim was invoked instead of bmad-prd. It is shown in your configured communication language and can be silenced by migrating your customization file and calling bmad-prd directly.