skills.rest
curdx
curdxCOMMUNITY
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.

4|Updated Apr 26, 2026
Search Tags:#acceptance criteria#epics#user stories#product planning#requirements decomposition#UX requirements#spec to delivery
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill bmad-create-epics-and-stories-curdx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/curdx/curdx-flow/tree/main/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/curdx/curdx-flow --skill bmad-create-epics-and-stories-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the gap between raw PRD/architecture/UX requirements and actionable, reviewable work breakdowns that Claude Code (or a developer agent) can implement without guesswork or missing acceptance criteria.

Core Features & Use Cases

  • Breaks requirements into epics and user stories: Decomposes FRs/NFRs plus Architecture and optional UX Design Requirements into implementable stories.
  • Creates acceptance-criteria-first stories: Produces Given/When/Then acceptance criteria so completion is verifiable rather than assumed.
  • Enforces a disciplined, stepwise workflow: Validates inputs, designs an epic structure for user value, then generates stories sequentially with explicit user approvals.
  • Produces a structured planning artifact: Initializes and fills a planning document at {planning_artifacts}/epics.md using a consistent template.

Quick Start

Ask the system to run bmad-create-epics-and-stories to transform your PRD (and Architecture, plus UX if available) into an epics and stories breakdown with acceptance criteria.

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 with acceptance criteria?▼

Breaking down a PRD into epics and user stories requires decomposing functional and non-functional requirements into implementable stories with Given/When/Then acceptance criteria. This produces a structured planning artifact with verifiable completion standards.

What is the best way to write user stories that are ready for developer agents?▼

Writing dev-ready user stories involves creating acceptance-criteria-first stories using Given/When/Then formats so completion is verifiable rather than assumed. This enforces a disciplined, stepwise workflow validating inputs before generating stories sequentially.

Can I generate an epic and story breakdown from architecture and UX requirements together?▼

You can generate an epic and story breakdown by combining PRD, Architecture, and optional UX Design Requirements as inputs. The process validates all available inputs, designs an epic structure for user value, then maps story coverage to the requirements inventory.

Does this requirements decomposition approach create forward dependencies between stories?▼

No, this requirements decomposition approach explicitly generates template-compliant stories without forward dependencies between them. It structures stories sequentially with explicit user approvals while maintaining independent implementation paths for Claude Code delivery.

How do I map epic coverage to ensure all requirements are captured in stories?▼

Mapping epic coverage involves extracting a requirements inventory from the PRD and Architecture, then validating that every functional and non-functional requirement maps to generated stories. This ensures complete traceability from spec to delivery without missing work items.

Related Skills

Explore More Product & Management Skills→
JingyiWngJingyiWng

bmad-check-implementation-readiness

Validate implementation readiness of PRD, UX, architecture, and epics.

Community
Advanced
LumenWipeLumenWipe
3

create-epics-and-stories

Break down PRDs and specs into epics and user stories with acceptance criteria.

Official
Advanced
AhmedKaram50AhmedKaram50

bmad-create-epics-and-stories

Decompose project requirements into structured epics and stories with acceptance criteria.

Community
Advanced
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate