Bmad Edit Prd
- 291 installs
- 51.5k repo stars
- Updated August 5, 2026
- bmad-code-org/bmad-method
bmad-edit-prd is a deprecated BMAD Method compatibility skill that forwards PRD update workflows to bmad-prd for developers refining goals, acceptance criteria, and dependencies in an existing spec.
About
bmad-edit-prd is a thin compatibility shim in bmad-code-org/bmad-method that forwards update-intent PRD work to the consolidated bmad-prd skill. BMAD consolidated bmad-create-prd, bmad-edit-prd, and bmad-validate-prd into one bmad-prd workflow supporting Create, Update, and Validate intents with facilitated discovery, validation checklists, and HTML report rendering. When invoked, bmad-edit-prd resolves legacy customization from _bmad/custom/bmad-edit-prd.toml—activation steps, persistent facts, and on_complete hooks—then hands the conversation to bmad-prd with intent locked to update. Developers still on bmad-edit-prd should migrate to bmad-prd directly for full template, checklist, and external handoff options. The shim exists so existing project overrides keep working until removal in BMAD v7.
- Structures goals, users, and success metrics in PRD form
- Clarifies acceptance criteria and explicit non-goals
- Surfaces dependency and sequencing gaps early
- Aligns stakeholders on a build-ready requirements doc
- Fits BMAD method’s spec-first product workflow
Bmad Edit Prd by the numbers
- 291 all-time installs (skills.sh)
- Ranked #917 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bmad-code-org/bmad-method --skill bmad-edit-prdAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 291 |
|---|---|
| repo stars | ★ 51.5k |
| Last updated | August 5, 2026 |
| Repository | bmad-code-org/bmad-method ↗ |
How do you update an existing PRD acceptance criteria?
Refine an existing PRD—tighten goals, acceptance criteria, out-of-scope items, and dependencies—so engineering can estimate and build against a single coherent spec.
Who is it for?
Product managers or tech leads maintaining BMAD PRDs who already invoke bmad-edit-prd or have legacy bmad-edit-prd.toml customization files.
Skip if: Greenfield PRD creation or validation-only reviews—use bmad-prd create or validate intents directly instead of this deprecated shim.
When should I use this skill?
A developer invokes bmad-edit-prd by name or asks to refine, update, or reconcile an existing PRD spec with new requirements.
What you get
Updated prd.md, addendum.md, and decision-log.md reconciled against the submitted change signal.
- Updated prd.md
- addendum.md
- decision-log.md
By the numbers
- Consolidated from 3 legacy PRD skills into unified bmad-prd workflow
- Update flow produces prd.md, addendum.md, and decision-log.md
Files
DEPRECATED — forwards to bmad-prd (update intent)
This skill was consolidated into bmad-prd. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-edit-prd.toml override files keep working. New work should invoke bmad-prd directly — it detects create / update / validate intent from the conversation.
On Activation
1. Resolve customization: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-edit-prd.toml and bmad-edit-prd.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).
2. Load {project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present) to resolve {user_name} and {communication_language}.
3. Emit a deprecation notice to the user in {communication_language}:
Notice:bmad-edit-prdis deprecated and will be removed in a future release. It now forwards tobmad-prdwith update intent. To silence this notice and access the full new customization surface (prd_template,validation_checklist,doc_standards,external_sources,external_handoffs,output_dir,output_folder_name), migrate_bmad/custom/bmad-edit-prd.tomlto_bmad/custom/bmad-prd.tomland invokebmad-prddirectly next time. Customization fields that were in this version still remain in the new version and will be respected if present in_bmad/custom/bmad-prd.toml, but the new version also supports additional fields that you can take advantage of by migrating.
4. Invoke bmad-prd with the following context. Pass these as the activating context so bmad-prd honors them instead of resolving its own customization from scratch:
- Intent:
update— skipbmad-prd's usual intent detection step. - Pre-resolved legacy customization — use these in place of resolving from
bmad-prd's owncustomize.tomlfor the four legacy fields. For everything else (prd_template,validation_checklist,validation_report_template,doc_standards,output_dir,output_folder_name,external_sources,external_handoffs), usebmad-prd's own defaults and overrides as normal: activation_steps_prepend= the resolved value from step 1activation_steps_append= the resolved value from step 1persistent_facts= the resolved value from step 1on_complete= the resolved value from step 1- Original user input: forward whatever the user said when invoking this skill verbatim (the target PRD path, the change signal, etc.).
bmad-prd takes the workflow from here. Do not execute any further steps in this shim.
# DO NOT EDIT -- overwritten on every update.
#
# Workflow customization surface for bmad-edit-prd. Mirrors the
# agent customization shape under the [workflow] namespace.
[workflow]
# --- Configurable below. Overrides merge per BMad structural rules: ---
# scalars: override wins • arrays (persistent_facts, activation_steps_*): append
# arrays-of-tables with `code`/`id`: replace matching items, append new ones.
# Steps to run before the standard activation (config load, greet).
# Overrides append. Use for pre-flight loads, compliance checks, etc.
activation_steps_prepend = []
# Steps to run after greet but before the workflow begins.
# Overrides append. Use for context-heavy setup that should happen
# once the user has been acknowledged.
activation_steps_append = []
# Persistent facts the workflow keeps in mind for the whole run
# (standards, compliance constraints, stylistic guardrails).
# Distinct from the runtime memory sidecar — these are static context
# loaded on activation. Overrides append.
#
# Each entry is either:
# - a literal sentence, e.g. "All PRDs must include a regulatory-risk section."
# - a file reference prefixed with `file:`, e.g. "file:{project-root}/docs/standards.md"
# (glob patterns are supported; the file's contents are loaded and treated as facts).
persistent_facts = [
"file:{project-root}/**/project-context.md",
]
# Scalar: executed when the workflow reaches Step E-4 (Complete & Validate) and the
# user exits via [S] Summary or [X] Exit — not on [V] Validate (which chains to
# bmad-validate-prd) or [E] Edit More (which loops back). Override wins.
# Leave empty for no custom post-completion behavior.
on_complete = ""
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Pick bmad-prd directly over bmad-edit-prd when starting new work so customization covers templates, validation checklists, and external handoffs.
FAQ
Is bmad-edit-prd still the recommended PRD update skill?
bmad-edit-prd is deprecated and consolidated into bmad-prd, which handles Create, Update, and Validate intents in one skill. bmad-edit-prd remains a compatibility shim that forwards update requests and legacy bmad-edit-prd.toml overrides to bmad-prd until BMAD v7 removal.
What files does a bmad-edit-prd update produce?
bmad-edit-prd delegates to bmad-prd, which reconciles change signals against an existing PRD and outputs updated prd.md plus supporting addendum.md and decision-log.md artifacts that preserve scope decisions and audit history.