Bmad Create Prd
- 353 installs
- 51.5k repo stars
- Updated August 5, 2026
- bmad-code-org/bmad-method
bmad-create-prd is an agent skill that authors a structured Product Requirements Document with goals, users, requirements, success metrics, constraints, and release scope for developers who need stakeholder-ready specs b
About
bmad-create-prd is a BMAD Method agent skill that turns rough product ideas into a structured Product Requirements Document covering goals, target users, functional requirements, success metrics, constraints, and release scope. The skill walks an AI coding agent through BMAD-style PRD sections so outputs are consistent enough for design, engineering, and stakeholder review without ad-hoc markdown templates. Developers reach for bmad-create-prd when kicking off a feature, MVP, or internal tool and need a single source of truth that downstream skills or teammates can implement against. It fits early planning in SaaS, API, and agent-backed products where ambiguous scope causes rework. Pair it with architecture or implementation skills after the PRD is approved rather than using it mid-refactor.
- Problem statement, personas, and outcome-oriented goals
- Functional and non-functional requirements with priorities
- Success metrics, assumptions, and dependency capture
- Release scope boundaries and explicit out-of-scope items
- Stakeholder-ready PRD formatted for architecture and story breakdown
Bmad Create Prd by the numbers
- 353 all-time installs (skills.sh)
- Ranked #832 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-create-prdAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 353 |
|---|---|
| repo stars | ★ 51.5k |
| Last updated | August 5, 2026 |
| Repository | bmad-code-org/bmad-method ↗ |
How do you write a structured PRD for a new feature?
Author a structured PRD with goals, users, requirements, success metrics, constraints, and release scope to guide design, build, and stakeholder approval.
Who is it for?
Developers or tech leads starting a new feature or product who need a stakeholder-ready requirements document before design and implementation.
Skip if: Teams that already have an approved PRD or only need low-level API schema or test scaffolding without product scope.
When should I use this skill?
The user asks to create, draft, or refine a PRD, product requirements, feature scope, or success metrics before build work starts.
What you get
Structured PRD document with goals, users, requirements, success metrics, constraints, and release scope
- Structured PRD markdown document
Files
DEPRECATED — forwards to bmad-prd (create 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-create-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-create-prd.toml and bmad-create-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-create-prdis deprecated and will be removed in a future release. It now forwards tobmad-prdwith create 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-create-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:
create— 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.
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-create-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 12 (Workflow Completion),
# after the PRD is finalized and workflow status is updated. 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.493kFAQ
What sections does bmad-create-prd include in a PRD?
bmad-create-prd produces a structured PRD with goals, target users, requirements, success metrics, constraints, and release scope. Each section is written for stakeholder review and to guide subsequent design and implementation work.
When should developers use bmad-create-prd in a project?
bmad-create-prd fits the start of a feature or product when scope is still ambiguous. Run it before UI design or coding so engineering, design, and stakeholders share one requirements document.