bmad-edit-prd

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-edit-prd-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-edit-prd
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-edit-prd
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-edit-prd-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for teams still invoking the deprecated bmad-edit-prd command, ensuring existing customizations and override files keep working while the workflow has been consolidated into bmad-prd. ## Core Features & Use Cases - Deprecation Forwarding: Emits a deprecation notice in the user's configured language and transparently forwards the invocation to bmad-prd with update intent. - Legacy Customization Resolution: Resolves legacy override fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) from _bmad/custom/bmad-edit-prd.toml via the resolve_customization.py script. - Use Case: A team with an existing bmad-edit-prd.toml override invokes the old skill name; the shim loads their customizations, warns about deprecation, and hands off to bmad-prd so their PRD update proceeds without breaking changes. ## 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 the BMad method?▼

Invoke bmad-prd directly with the target PRD path and your change description; it detects update intent automatically. The deprecated bmad-edit-prd skill still works but simply forwards to bmad-prd after showing a deprecation notice.

What happened to the bmad-edit-prd skill?▼

bmad-edit-prd was consolidated into bmad-prd and is now a thin compatibility shim. It will be removed in v7, so new work should invoke bmad-prd directly, which detects create, update, and validate intent from conversation.

Will my bmad-edit-prd.toml customizations still work?▼

Yes, the shim resolves legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete) from _bmad/custom/bmad-edit-prd.toml and passes them 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 override file from _bmad/custom/bmad-edit-prd.toml to _bmad/custom/bmad-prd.toml and invoke bmad-prd directly. The new version supports extra fields like prd_template, validation_checklist, doc_standards, and output_dir.

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

The notice appears because you invoked the deprecated bmad-edit-prd skill, which now forwards to bmad-prd. To silence it, migrate your customization file to bmad-prd.toml and call bmad-prd directly next time.