bmad-create-epics-and-stories

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

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-create-epics-and-stories-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-create-epics-and-stories-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD, architecture document, and UX design into a developer-ready backlog is slow and error-prone; this Skill guides a structured, step-by-step breakdown of requirements into epics and stories with testable acceptance criteria. ## Core Features & Use Cases - Requirements Extraction: Validates and extracts functional requirements, non-functional requirements, architecture constraints, and UX design requirements from planning documents. - Epic Design: Organizes requirements into user-value-focused epics with a full FR coverage map and explicit user approval gates. - Story Generation: Creates sequentially independent stories in Given/When/Then acceptance criteria format, sized for a single dev agent. - Use Case: After finishing a PRD and architecture for a new product, run this workflow to produce a complete epics.md backlog ready for the Developer agent. ## Quick Start Ask the agent to create the epics and stories list from the PRD and architecture documents in the planning artifacts folder.

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 in the planning artifacts folder, then ask to create the epics and stories list. The workflow extracts all FRs and NFRs, proposes a user-value-based epic structure for approval, then generates stories with Given/When/Then acceptance criteria.

What documents are required before creating epics and stories?▼

A PRD containing functional and non-functional requirements and an architecture document are required. A UX design contract is optional but recommended, since UX design requirements are extracted as first-class inputs and must be covered by stories.

How are user stories formatted in the generated backlog?▼

Each story uses the As a / I want / So that format followed by acceptance criteria written in Given/When/Then style. Stories are sized for a single dev agent and must not depend on future stories within the same epic.

Can I customize the epic creation workflow for my team?▼

Yes, the customize.toml file supports team and user-level overrides for activation steps, persistent facts, and post-completion behavior. Overrides merge structurally, with scalars replacing defaults and arrays appending.

What happens if requirements are missing from the generated stories?▼

The final validation step checks that every FR maps to at least one story, verifies story dependencies flow only backward, and confirms epics deliver standalone user value. Incomplete coverage blocks workflow completion until resolved.