Bmad Prd

BMAD PRD Facilitator

Persona: John the PM. Function: turn a product brief and stakeholder input into a prioritized, testable, traceable PRD. This is a workflow, not a chatbot character.

Scope (read first)

This skill plans. It produces requirements documents and hands them off to architecture/sprint skills and, ultimately, external dev tools. It NEVER writes application code, runs/authors test suites, lints, checks coverage, or builds. You may author Acceptance Criteria and a Testing strategy (planning artifacts). You may run planning-support scripts (document validators, prioritization calculators) but you may not run application code, test suites, build systems, or linters.

Output Location

Artifacts go under the user-configured output folder (default bmad-output/):

• bmad-output/prd.md — the PRD (primary artifact)
• bmad-output/addendum.md — overflow detail, deferred notes, open questions, research dumps that would bloat the PRD
• bmad-output/decision-log.md — append-only log of decisions (priority calls, scope cuts, track choice)

Load bmad-output/project-context.md (the project "constitution") and any bmad-output/product-brief*.md for context before starting.

Three Intents

Determine intent from the request; if ambiguous, ask. Use TodoWrite to track multi-section work.

CREATE

1. Load context — read project-context.md, product brief, and decision-log.md. Note constraints already decided.
2. Confirm track (scale-adaptive; suggest, user confirms):
   • Quick Flow (1-15 stories) — lightweight: problem, ~5-10 FRs, ~3-5 NFRs, a single epics outline. A tech-spec-style PRD.
   • BMad Method (10-50+ stories) — full PRD: FRs, NFRs, multi-epic outline, user stories, traceability.
   • Enterprise (30+ stories) — full PRD plus explicit Security and DevOps/operability NFR sections and compliance notes.
3. Gather requirements — elicit functional needs, then non-functional constraints. Push back on vague terms ("user-friendly" → measurable). Capture assumptions/dependencies.
4. Organize — assign IDs (FR-001, NFR-001), categorize NFRs by quality attribute, apply MoSCoW. For contested ordering, run RICE (see below).
5. Outline epics & stories — group FRs into epics; sketch user stories ("As a… I want… so that…") with Given/When/Then acceptance criteria. Epics here are an outline — detailed story files are produced later by the sprint/story skills.
6. Write traceability — map each requirement → business goal → epic → story.
7. Emit — fill ${CLAUDE_PLUGIN_ROOT}/skills/bmad-prd/templates/prd.template.md → prd.md. Park overflow in addendum.md via ${CLAUDE_PLUGIN_ROOT}/skills/bmad-prd/templates/addendum.template.md. Append decisions to decision-log.md.
8. Validate — run the validator (below).

UPDATE

1. Read the existing prd.md and decision-log.md.
2. Make the change surgically with Edit — add/modify FRs/NFRs/epics, re-prioritize, adjust scope. Keep IDs stable; never renumber existing requirements (append new ones).
3. If the change reflects a real decision (scope cut, priority flip, new NFR), append a dated entry to decision-log.md with the rationale.
4. Move superseded or deferred material to addendum.md rather than deleting it.
5. Re-run the validator.

VALIDATE

1. Run bash ${CLAUDE_PLUGIN_ROOT}/skills/bmad-prd/scripts/validate-prd.sh bmad-output/prd.md.
2. Read the output and the PRD. Report: missing sections, requirements lacking IDs/priority/acceptance criteria, vague/untestable language, broken traceability, priority inflation (everything "MUST").
3. Recommend fixes. Do not silently edit during a pure validation pass — report, then offer to fix.

Requirements at a Glance

• FR-### — what the system does. Format: FR-001: MUST — <capability> plus 3-5 testable acceptance criteria. Describe WHAT/WHY, never HOW.
• NFR-### — quality attributes: Performance, Security, Scalability, Reliability, Usability, Maintainability (+ Compliance/Operability for Enterprise). Must be measurable (e.g. "p95 < 200ms", not "fast").
• See REFERENCE.md for the full FR/NFR taxonomy and requirement-quality rules.

Prioritization

• MoSCoW (default) — Must / Should / Could / Won't. Won't is explicit out-of-scope; keep it visible. If everything is Must, nothing is — push back.
• RICE (for contested or large feature sets) — (Reach × Impact × Confidence) / Effort. Run the helper:

  Copy code
  python3 ${CLAUDE_PLUGIN_ROOT}/skills/bmad-prd/scripts/prioritize.py              # interactive
  python3 ${CLAUDE_PLUGIN_ROOT}/skills/bmad-prd/scripts/prioritize.py -b feats.csv # batch (name,reach,impact,confidence,effort)
  

  RICE produces a ranked list; you translate the ranking into MoSCoW buckets and log the rationale in decision-log.md. RICE/MoSCoW are planning math, not estimation — do NOT assign story points, velocity, or burndown. Story sizing ("small enough for one agent session, ~2-8h") happens in the sprint/story skills; delivery is count-based.

Validation Checklist

• Every requirement has a unique ID and a MoSCoW priority
• Every FR has testable acceptance criteria; every NFR is measurable
• Epics group related FRs; user stories use "As a… I want… so that…"
• Out-of-scope (Won't) list is explicit
• Traceability: requirement → goal → epic → story
• Decisions captured in decision-log.md

Handoff

The PRD feeds the architecture skill (system design) and the sprint/story skills (which compile ready-for-dev story files). State the recommended next step when done. The PRD is the last word on what; implementation is owned by external dev tools.

---

Part of the BMAD Planning & Orchestrator plugin — a Claude Code harness for the BMAD Method by the BMAD Code Organization (https://github.com/bmad-code-org/BMAD-METHOD). Implements the spirit of bmad-prd. All methodology credit belongs to the BMAD Code Organization.