Bmad Validate Prd
- 296 installs
- 51.5k repo stars
- Updated August 5, 2026
- bmad-code-org/bmad-method
bmad-validate-prd is a BMAD Method agent skill that reviews and stress-tests a PRD for completeness, feasibility, and BMAD methodology alignment for developers who need scope validation before coding starts.
About
bmad-validate-prd is a bmad-code-org/bmad-method skill that audits product requirement documents before any implementation work begins. It checks PRDs for completeness, technical feasibility, and alignment with BMAD spec-driven methodology so downstream sprint planning and quick-dev sessions start from sound requirements. The standard BMAD Method track requires PRDs and architecture before coding, unlike the Quick Flow track for small bug fixes needing only a tech spec. Reach for bmad-validate-prd when a draft PRD exists but needs gap analysis, contradiction checks, or feasibility stress-testing before engineers and agents commit to build scope. The skill acts as a scope gate between domain research and sprint planning, catching missing acceptance criteria, unstated constraints, or misaligned agent workflows early. Outputs include annotated PRD feedback ready for revision or approval.
- Checks PRD completeness against BMAD standards
- Flags ambiguous or untestable requirements
- Surfaces missing acceptance criteria
- Aligns scope with methodology gates
- Reduces rework from weak specs
Bmad Validate Prd by the numbers
- 296 all-time installs (skills.sh)
- Ranked #909 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-validate-prdAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 296 |
|---|---|
| repo stars | ★ 51.5k |
| Last updated | August 5, 2026 |
| Repository | bmad-code-org/bmad-method ↗ |
How do you validate a PRD with BMAD Method?
Review and stress-test a PRD for completeness, feasibility, and alignment with BMAD methodology before development starts.
Who is it for?
Developers with a draft PRD on the BMAD standard track who need structured validation before sprint planning or coding.
Skip if: Quick Flow bug fixes that require only a technical spec without a formal PRD document.
When should I use this skill?
A draft PRD exists and the user needs completeness, feasibility, or BMAD methodology review before development starts.
What you get
Annotated PRD review with completeness gaps, feasibility flags, and BMAD alignment recommendations.
- PRD validation report
- Completeness gap list
- Feasibility recommendations
By the numbers
- Gates BMAD standard track PRDs before architecture and implementation phases
Files
DEPRECATED — forwards to bmad-prd (validate 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-validate-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-validate-prd.toml and bmad-validate-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-validate-prdis deprecated and will be removed in a future release. It now forwards tobmad-prdwith validate 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-validate-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:
validate— 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, 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-validate-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 13 (Validation Report Complete) and
# the user exits via [X] Exit — not on [E] Use Edit Workflow (which chains to
# bmad-edit-prd), [R] Review (which loops within), or [F] Fix (which loops within).
# 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-validate-prd when a PRD needs formal scope gating instead of jumping directly to bmad-sprint-planning or bmad-quick-dev.
FAQ
What does bmad-validate-prd check in a PRD?
bmad-validate-prd checks PRDs for completeness, technical feasibility, and alignment with BMAD methodology. The skill identifies missing acceptance criteria, contradictions, and unstated constraints before sprint planning or implementation workflows begin.
Is bmad-validate-prd required for BMAD Quick Flow?
bmad-validate-prd targets the BMAD standard Method track where PRDs precede architecture and coding. Quick Flow work for small features and bug fixes typically needs only a technical specification, not full PRD validation.