bmad-create-epics-and-stories

Decomposes PRD and architecture requirements into epics and user stories with acceptance criteria.

Updated Aug 25, 2024
One-click install
npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-create-epics-and-stories-legerycheese
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot/tree/main/bmad/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-create-epics-and-stories-legerycheese

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD and architecture document into an actionable backlog is slow and error-prone; this Skill guides a structured, step-by-step workflow that extracts every requirement and converts it into validated epics and stories. ## Core Features & Use Cases - Requirements Extraction: Pulls functional requirements, non-functional requirements, architecture constraints, and UX design requirements from planning documents into a requirements inventory. - Epic Design with Coverage Mapping: Organizes requirements into user-value-focused epics and builds an FR coverage map so no requirement is missed. - Story Generation with Acceptance Criteria: Creates Given/When/Then acceptance criteria for each story, sized for a single developer agent, with dependency validation. - Use Case: After finishing a PRD and architecture spec for a new app, run this workflow to produce a complete epics.md file with validated stories ready for development. ## Quick Start Ask the agent to create the epics and stories list from your PRD and architecture documents.

Frequently Asked Questions about bmad-create-epics-and-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a PRD into epics and user stories?▼

Provide your PRD, architecture document, and optional UX design spec, then follow the guided workflow. It extracts all functional and non-functional requirements, groups them into user-value-focused epics, and generates stories with testable acceptance criteria.

What documents are required to create epics and stories?▼

A PRD containing functional and non-functional requirements and an architecture document are required. A UX design specification is optional but recommended, as its requirements are extracted as first-class inputs for story creation.

How are acceptance criteria written for user stories?▼

Acceptance criteria use the Given/When/Then format, with each criterion independently testable. The workflow includes edge cases and error conditions, and each story is sized to be completable by a single developer agent.

Does the workflow check that all requirements are covered?▼

Yes, a final validation step verifies every functional requirement maps to at least one story, checks story dependencies flow only forward, and confirms epics deliver standalone user value without forward dependencies.

Can I customize the epic and story creation workflow?▼

Yes, a customize.toml file supports team and user overrides for activation steps, persistent facts, and post-completion behavior. Overrides merge with defaults using structural rules for scalars, tables, and arrays.