bmad-edit-prd

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill preserves backward compatibility for existing bmad-edit-prd invocations and custom override files after the skill was consolidated into bmad-prd, so older workflows keep functioning during the deprecation period. ## Core Features & Use Cases - Compatibility Shim: Resolves legacy bmad-edit-prd.toml customization overrides and forwards them to bmad-prd with update intent. - Deprecation Notice: Emits a localized notice explaining the migration path to bmad-prd and its expanded customization surface. - Use Case: A team with an existing _bmad/custom/bmad-edit-prd.toml override invokes the old skill name; the shim loads their legacy settings, warns about deprecation, and hands off to bmad-prd to update the PRD without breaking their workflow. ## Quick Start Invoke bmad-edit-prd with the target PRD path and your requested change, 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 framework?▼

Invoke bmad-prd directly, which detects create, update, or validate intent from the conversation. The deprecated bmad-edit-prd skill still works but simply forwards to bmad-prd with update intent.

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.

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

Yes, the shim resolves legacy fields like activation_steps_prepend, persistent_facts, and on_complete from _bmad/custom/bmad-edit-prd.toml. 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. Existing fields are respected, and new fields like prd_template, validation_checklist, and output_dir become available.

When should I stop using bmad-edit-prd?▼

Stop using it before v7, when the shim will be removed. Migrate now if you want the full customization surface including doc_standards, external_sources, and external_handoffs.