Menu
Deprecated — forwards to bmad-prd (update intent).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Strategic business analyst and requirements expert. Use when the user asks to talk to Mary or requests the business analyst.
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
Deprecated — forwards to bmad-deep-recon (domain type).
Deprecated — forwards to bmad-deep-recon (market type).
Deprecated — forwards to bmad-deep-recon (technical type).
Decision-grade research, three ways: draft a deep-research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), process a finished research report — file it, distill a succinct cited summary with metadata that downstream skills consume without reprocessing — or run the research here through web fan-out. Shipped type packs: market, domain, technical, competitive, user-voice, academic-lit — plus a select shape for choose-between decisions and custom types via overrides. Use when the user says "deep recon", "research this", "draft a research prompt", "process this research report", "market research", "domain research", "technical research", "competitor research", "literature review", or "help me choose between".
| name | bmad-edit-prd |
| description | 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.
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_template,validation_report_template,doc_standards,finalize_reviewers,external_sources,external_handoffs,prd_output_path,run_folder_pattern), 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_template, validation_report_template, doc_standards, finalize_reviewers, prd_output_path, run_folder_pattern, 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.