skills.rest
enigmaicon-eng
enigmaicon-engCOMMUNITY
Explore all skills by this author →
GitHub

bmad-create-epics-and-stories

Break PRD and Architecture requirements into epics and user stories with acceptance criteria.

1|Updated May 16, 2026
Search Tags:#architecture#acceptance criteria#epics#PRD#user stories#requirements decomposition#UX integration
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-create-epics-and-stories-enigmaicon-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/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/BMAD-METHOD/src/bmm-skills/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill bmad-create-epics-and-stories-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly convert PRD and Architecture inputs into an organized, developer-ready epic and user-story backlog with clear acceptance criteria.

Core Features & Use Cases

  • Requirements decomposition: Breaks PRD functional and non-functional requirements into epics and implementable user stories.
  • Developer-ready acceptance criteria: Produces Given/When/Then acceptance criteria suitable for single-dev-agent execution.
  • Optional UX requirement integration: Includes UX Design Requirements when provided, ensuring they are covered by stories.
  • Disciplined workflow: Uses a step-driven process with explicit menus to confirm extracted requirements and approved epic structure.

Quick Start

Ask the agent to create the epics and stories list after providing PRD.md, Architecture.md, and (if available) UX Design.md.

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 down a PRD into epics and user stories?▼

To break down a PRD into epics and user stories, you extract functional and non-functional requirements, organize them by user value, and decompose them into sequential stories with Given/When/Then acceptance criteria.

What is requirements decomposition for developer-ready user stories?▼

Requirements decomposition is the process of mapping PRD and Architecture inputs for coverage, then splitting them into single-agent-completable user stories that include structured acceptance criteria for downstream development.

How do I integrate UX design requirements into user stories?▼

You integrate UX design requirements by providing a UX Design document as input alongside the PRD and Architecture, ensuring UX design requirements are explicitly covered by the generated epics and actionable user stories.

Do I need an Architecture document to generate user stories from a PRD?▼

Yes, you need an Architecture document alongside the PRD to map technical constraints and ensure the generated user stories are actionable and single-agent-completable for downstream development.

What is the best way to write acceptance criteria for epics and stories?▼

The best way to write acceptance criteria for epics and stories is using the Given/When/Then format, which produces clear, testable conditions suitable for single-dev-agent execution and downstream development.

Related Skills

Explore More Product & Management Skills→
korchasakorchasa
1

flowai-skill-write-prd

Draft structured PRDs from stakeholder inputs and save them to disk.

Community
Advanced
ximingximing

ralph

Convert Product Requirement Documents into structured prd.json for Ralph.

Community
Intermediate
ncptuanncptuan

bmad-create-epics-and-stories

Break product requirements into epics and user stories with acceptance criteria.

Community
Advanced
tiweentiween

bmad-check-implementation-readiness

Validate PRD, UX, Architecture, and Epics documents for implementation readiness.

Official
Advanced