BMAD-METHOD/create-prd.md at efbe839a0a9752a3ac6ffa8b4785b290119be2d2

mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00

Files

forcetrainer e535f94325 docs: comprehensive style guide update with reference and glossary standards

Style Guide Additions:
- Add Reference Structure section with 6 document types (Index, Catalog,
  Deep-Dive, Configuration, Glossary, Comprehensive)
- Add Glossary Structure section with table-based format leveraging
  Starlight's right-nav for navigation
- Include checklists for both new document types

Reference Docs Updated:
- agents/index.md: Catalog format, universal commands tip admonition
- configuration/core-tasks.md: Configuration format with admonitions
- configuration/global-config.md: Table-based config reference
- workflows/index.md: Minimal index format
- workflows/core-workflows.md: Catalog format
- workflows/document-project.md: Deep-dive with Quick Facts admonition
- workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules

Glossary Rewritten:
- Converted from 373 lines with ### headers to 123 lines with tables
- Right nav now shows 9 categories instead of 50+ terms
- Added italic context markers (*BMGD.*, *Brownfield.*, etc.)
- Alphabetized terms within categories
- Removed redundant inline TOC

All Docs:
- Remove horizontal rules (---) per style guide
- Remove "Related" sections (sidebar handles navigation)
- Standardize admonition usage
- Archive deleted workflow customization docs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-12 00:23:05 -05:00

2.3 KiB

Raw Blame History

title, description

title	description
How to Create a PRD	How to create a Product Requirements Document using the BMad Method

Use the prd workflow to create a strategic Product Requirements Document with Functional Requirements (FRs) and Non-Functional Requirements (NFRs).

When to Use This

Medium to large feature sets
Multi-screen user experiences
Complex business logic
Multiple system integrations
Phased delivery required

:::note[Prerequisites]

BMad Method installed
PM agent available
Optional: Product brief from Phase 1 :::

Steps

1. Load the PM Agent

Start a fresh chat and load the PM agent.

2. Run the PRD Workflow

*create-prd

3. Provide Context

The workflow will:

Load any existing product brief
Ask about your project scope
Gather requirements through conversation

4. Define Requirements

Work with the agent to define:

Functional Requirements (FRs) — What the system should do
Non-Functional Requirements (NFRs) — How well it should do it

5. Review the PRD

The agent produces a comprehensive PRD scaled to your project.

What You Get

A PRD.md document containing:

Executive summary
Problem statement
User personas
Functional requirements (FRs)
Non-functional requirements (NFRs)
Success metrics
Risks and assumptions

Scale-Adaptive Structure

The PRD adapts to your project complexity:

Scale	Pages	Focus
Light	10-15	Focused FRs/NFRs, simplified analysis
Standard	20-30	Comprehensive FRs/NFRs, thorough analysis
Comprehensive	30-50+	Extensive FRs/NFRs, multi-phase, stakeholder analysis

Example

E-commerce checkout → PRD with:

15 FRs (user account, cart management, payment flow)
8 NFRs (performance, security, scalability)

Tips

Do Product Brief first — Run product-brief from Phase 1 for better results
Focus on "What" not "How" — Planning defines what to build and why. Leave how (technical design) to Phase 3
Document-Project first for Brownfield — Always run document-project before planning brownfield projects. AI agents need existing codebase context

Next Steps

After PRD:

Create UX Design (optional) — If UX is critical
Create Architecture — Technical design
Create Epics and Stories — After architecture

2.3 KiB Raw Blame History