skills.rest
Hexalith
HexalithOFFICIAL
Explore all skills by this author →
WebsiteGitHub

bmad-create-epics-and-stories

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

Updated Mar 1, 2026
Search Tags:#requirements#acceptance criteria#epics#user stories#backlog#prd#agile planning
One-click install
npx skills add https://github.com/Hexalith/Hexalith.Parties --skill bmad-create-epics-and-stories-hexalith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/Hexalith/Hexalith.Parties/tree/main/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/Hexalith/Hexalith.Parties --skill bmad-create-epics-and-stories-hexalith

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 approved epics and developer-ready stories. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX design documents to inventory functional, non-functional, and UX design requirements. - Epic Design: Groups requirements into user-value-focused epics with an FR coverage map, validated collaboratively with the user. - Story Generation: Produces stories in As a/I want/So that format with Given/When/Then acceptance criteria, sized for a single dev agent. - Use Case: After finishing a PRD for a new product, run this workflow to produce a complete epics.md with validated coverage of every requirement before development begins. ## 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?▼

Run this workflow after your PRD and architecture documents exist. It extracts all functional and non-functional requirements, proposes user-value-focused epics for your approval, then generates stories with testable acceptance criteria for each epic.

What documents are required to create epics and stories?▼

The workflow requires a PRD containing functional and non-functional requirements and an Architecture document with technical decisions. A UX design document is optional but treated as a first-class input when present.

How are user stories formatted in the output?▼

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

Does the workflow check that all requirements are covered?▼

Yes. The final validation step verifies every FR maps to at least one story, checks epic independence and story dependency ordering, and confirms UX design requirements are covered before completing.

Can I customize the epics and stories workflow behavior?▼

Yes. A customize.toml file supports activation step overrides, persistent facts loaded as context, and an on_complete hook, merged with team and user-level TOML overrides in the project.

Related Skills

Explore More Product & Management Skills→
Mte90Mte90
51

Product Requirements

Draft Product Requirements Documents through a structured Q&A process.

Community
Advanced
GenEducationGenEducation

bmad-create-story

Generate implementation-ready story files with acceptance criteria, tasks, and dev notes.

Official
Advanced
abhilash-nandkumarabhilash-nandkumar

user-story-fundamentals

Capture user requirements into structured user stories with acceptance criteria.

Community
Intermediate
Insik-HanInsik-Han
16

to-issues

Break plans, specs, or PRDs into vertical-slice issues for issue trackers.

Community
Intermediate