bmad-create-epics-and-stories

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

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill bmad-create-epics-and-stories-sevwren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/SevWren/Daily-Motivation-Brain-Helper/tree/main/.claude/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/SevWren/Daily-Motivation-Brain-Helper --skill bmad-create-epics-and-stories-sevwren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD and architecture document into an actionable backlog is slow and error-prone: requirements get missed, epics get organized by technical layers instead of user value, and stories lack testable acceptance criteria. This Skill guides a structured, step-by-step decomposition so every requirement maps to a story a developer can implement. ## Core Features & Use Cases - Requirements Extraction: Validates and extracts functional requirements, non-functional requirements, architecture constraints, and UX design requirements from PRD, Architecture, and UX documents. - Epic Design with Coverage Mapping: Organizes requirements into user-value-focused epics and produces an FR coverage map so no requirement is left unassigned. - Story Generation with Acceptance Criteria: Creates Given/When/Then acceptance criteria for each story, sized for a single dev agent, with dependency validation across epics and stories. - Use Case: After finishing a PRD and architecture for a new product, run this workflow to produce a complete epics.md with validated epics, stories, and acceptance criteria ready to hand to a developer agent. ## Quick Start Ask the assistant 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?

Run this workflow after your PRD and architecture documents exist. It extracts all functional and non-functional requirements, groups them into user-value-focused epics with your approval, then generates stories with Given/When/Then acceptance criteria for each epic.

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 document is optional but recommended, since UX requirements are extracted as first-class inputs and must be covered by stories.

How are epics organized in this workflow?

Epics are organized by user value rather than technical layers, and each epic must deliver complete standalone functionality. Epics that repeatedly modify the same core files are candidates for consolidation into a single epic with ordered stories.

Can stories depend on future stories in the same epic?

No. Each story must be completable using only the output of previous stories. The final validation step explicitly checks for forward dependencies and rejects stories that require future work to function.

What format do the acceptance criteria use?

Acceptance criteria use the Given/When/Then format, with each criterion independently testable. Stories follow the standard As a / I want / So that user story structure defined in the epics template.