bmad-create-epics-and-stories

Decompose PRD, Architecture, and UX requirements into structured epics and stories.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mschuerig/peach-ios --skill bmad-create-epics-and-stories-mschuerig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/mschuerig/peach-ios/tree/main/_bmad/bmm/workflows/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/mschuerig/peach-ios --skill bmad-create-epics-and-stories-mschuerig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to translate scattered PRDs, architecture decisions, and UX notes into actionable development work. This skill provides a principled workflow to decompose requirements into standalone epics and stories with explicit acceptance criteria.

Core Features & Use Cases

  • Transform functional and non-functional requirements into organized epic structures with clear traceability from FRs to stories
  • Map every FR to an epic, plus a requirements coverage map to ensure nothing is missed
  • Generate independent, testable stories per epic with exact Acceptance Criteria and one-developer scope
  • Follow a step-based workflow (validate-prerequisites, design-epics, create-stories, final-validate) to ensure consistency
  • Include UX design requirements when present and incorporate design tokens and accessibility considerations

Quick Start

Use Step 01 to begin the process: gather PRD.md, Architecture.md, UX Design.md, and confirm any exclusions, then proceed to Step-01 execution.

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 convert PRD and architecture requirements into actionable epics and stories?

You can decompose project requirements from PRD, architecture, and UX documents into structured epics and stories by mapping each functional requirement to an epic and generating independent, testable stories with measurable acceptance criteria.

What is the best way to ensure requirements coverage when generating epics from a PRD?

The best way to ensure requirements coverage is to generate a requirements coverage map that explicitly maps every functional requirement from the PRD directly to an epic, ensuring nothing is missed during delivery planning.

Do I need UX design documents to create actionable user stories?

UX design documents are not strictly required but are highly recommended. When present, the workflow incorporates UX design requirements, design tokens, and accessibility considerations directly into the generated stories.

How are acceptance criteria structured when decomposing requirements into stories?

Acceptance criteria are structured to be exact and measurable for each story. Every generated story is designed to be independent, testable, and scoped for a single developer to implement.

Can I use this workflow to validate prerequisites before designing epics?

Yes, the workflow follows a strict step-based process starting with prerequisites validation. You gather PRD, architecture, and UX documents and confirm exclusions before proceeding to epic design and story generation.

What happens if non-functional requirements are missing from my architecture documentation?

If non-functional requirements are missing, the final validation step checks for gaps in the requirements coverage map, allowing you to identify and address missing architecture or UX constraints before implementation.