bmad-create-epics-and-stories

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

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-create-epics-and-stories-tuanpa-nhg-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/tuanpa-nhg-eng/nhg-ipms/tree/main/.claude/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/tuanpa-nhg-eng/nhg-ipms --skill bmad-create-epics-and-stories-tuanpa-nhg-eng

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 workflow that extracts every requirement, groups them into user-value-focused epics, and writes stories with testable acceptance criteria. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX design documents (including sharded variants) to inventory FRs, NFRs, and UX design requirements. - Epic Design with Coverage Mapping: Organizes requirements into standalone, user-value epics and produces an FR-to-epic coverage map so nothing is missed. - Story Generation & Validation: Creates Given/When/Then acceptance criteria per story, then validates dependency ordering, sizing, and full requirement coverage. - Use Case: After finishing a PRD and architecture for a new product, run this workflow to produce a complete epics.md backlog 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 epics with your approval, then generates stories with Given/When/Then acceptance criteria saved to epics.md.

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 document is optional but treated as a first-class input, with its requirements extracted as separate UX-DR items.

Does the workflow support sharded PRD or architecture documents?

Yes. The document discovery step searches for whole documents first, then falls back to sharded folders with an index.md. It also supports bmad-ux spine pairs consisting of DESIGN.md and EXPERIENCE.md files.

How are story dependencies handled within an epic?

Stories must be independently completable in sequence, building only on previous stories. The final validation step explicitly checks for forward dependencies and rejects stories that require future stories to function.

What happens if requirements are missing from the story breakdown?

The final validation step performs an FR coverage check, verifying every functional requirement maps to at least one story with adequate acceptance criteria. Incomplete coverage blocks workflow completion until resolved.