Menu
DEPRECATED — consolidated into bmad-prd update intent - this skill will be removed in v7 in favor of `bmad-prd`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
One iteration of an unattended development loop. Use when invoked by name.
Distill any intent input into the SPEC kernel + companions — the canonical, preservation-validated machine contract for downstream work. Use when the user says "create a spec", "distill this into a spec", "validate this spec", "update the spec", or "break this into stories".
Adversarial code review using parallel review layers and structured triage. Use when the user says "run code review" or "review this code"
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
Review a code change for changed behavior that could regress without reliable verification catching it. Use when checking whether a change is adequately verified.
Analyzes current state and user query to answer BMad questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.
| name | bmad-edit-prd |
| description | DEPRECATED — consolidated into bmad-prd update intent - this skill will be removed in v7 in favor of `bmad-prd`. |
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.
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).
Load {project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present) to resolve {user_name} and {communication_language}.
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.
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:
update — skip bmad-prd's usual intent detection step.bmad-prd's own customize.toml for 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), use bmad-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 1bmad-prd takes the workflow from here. Do not execute any further steps in this shim.