ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
e535f943258eb9eb3ac94ce75c014e9a6be5442f
BMAD-METHOD/docs/how-to/workflows/create-epics-and-stories.md
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.9 KiB
Raw Blame History

title, description
title description
How to Create Epics and Stories How to break PRD requirements into epics and stories using BMad Method

Use the create-epics-and-stories workflow to transform PRD requirements into bite-sized stories organized into deliverable epics.

When to Use This

  • After architecture workflow completes
  • When PRD contains FRs/NFRs ready for implementation breakdown
  • Before implementation-readiness gate check

:::note[Prerequisites]

  • BMad Method installed
  • PM agent available
  • PRD completed
  • Architecture completed :::

Why After Architecture?

This workflow runs AFTER architecture because:

  1. Informed Story Sizing — Architecture decisions affect story complexity
  2. Dependency Awareness — Architecture reveals technical dependencies
  3. Technical Feasibility — Stories can be properly scoped knowing the tech stack
  4. Consistency — All stories align with documented architectural patterns

Steps

1. Load the PM Agent

Start a fresh chat and load the PM agent.

2. Run the Workflow

*create-epics-and-stories

3. Provide Context

Point the agent to:

  • Your PRD (FRs/NFRs)
  • Your architecture document
  • Optional: UX design artifacts

4. Review Epic Breakdown

The agent organizes requirements into logical epics with user stories.

5. Validate Story Quality

Ensure each story has:

  • Clear acceptance criteria
  • Appropriate priority
  • Identified dependencies
  • Technical notes from architecture

What You Get

Epic files (one per epic) containing:

  1. Epic objective and scope
  2. User stories with acceptance criteria
  3. Story priorities (P0/P1/P2/P3)
  4. Dependencies between stories
  5. Technical notes referencing architecture decisions

Example

E-commerce PRD with FR-001 (User Registration), FR-002 (Product Catalog) produces:

  • Epic 1: User Management (3 stories)

    • Story 1.1: User registration form
    • Story 1.2: Email verification
    • Story 1.3: Login/logout

  • Epic 2: Product Display (4 stories)

    • Story 2.1: Product listing page
    • Story 2.2: Product detail page
    • Story 2.3: Search functionality
    • Story 2.4: Category filtering

Each story references relevant ADRs from architecture.

Story Priority Levels

Priority Meaning
P0 Critical — Must have for MVP
P1 High — Important for release
P2 Medium — Nice to have
P3 Low — Future consideration

Tips

  • Keep stories small — Complete in a single session
  • Make criteria testable — Acceptance criteria should be verifiable
  • Document dependencies clearly — Know what blocks what
  • Reference architecture — Include ADR references in technical notes

Next Steps

After creating epics and stories:

  1. Implementation Readiness — Validate alignment before Phase 4
  2. Sprint Planning — Organize work for implementation