Verified:GitHub

bmad-create-epics-and-stories

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

36|16|Updated May 1, 2026

Search Tags:#acceptance criteria #epics #PRD #user stories #product planning #requirements decomposition #architecture mapping

Ready to run

npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-create-epics-and-stories-tronghieu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-create-epics-and-stories-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns PRD and architecture requirements into a clear, developer-ready epic and user-story plan with complete acceptance criteria, so teams don’t waste cycles translating requirements into implementation work.

Core Features & Use Cases

Requirements decomposition: Breaks FRs, NFRs, and architecture constraints into user-value epics and implementable stories.
Workflow-driven generation: Uses a disciplined step architecture with prerequisite validation, epic design approval, and story creation.
Quality-focused output: Produces stories sized for a single dev agent and ensures each story includes testable Given/When/Then acceptance criteria.

Quick Start

Use the bmad-create-epics-and-stories skill to convert your PRD requirements and Architecture decisions into an epics and stories list 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 PRD requirements into developer-ready user stories?▼

To break PRD requirements into developer-ready user stories, you map functional requirements and architecture constraints into user-value epics, then decompose them into independently completable stories with Given/When/Then acceptance criteria.

What is the best way to structure epics so user stories have no forward dependencies?▼

To structure epics without forward dependencies, you sequence user stories during requirements decomposition so each story is independently completable, ensuring implementation planning moves forward without blocking subsequent dev agent tasks.

How does mapping functional requirements to epics work for product planning?▼

Mapping functional requirements to epics for product planning works by validating prerequisite documents, designing epics for user value, and gating story creation through user confirmations to ensure full FR coverage.

Do I need an approved architecture document to generate user stories with acceptance criteria?▼

Yes, you need an approved architecture document and PRD to generate user stories with acceptance criteria, as the workflow applies prerequisite validation to map architecture constraints and NFRs into the story creation process.

Can I use this requirements decomposition approach for a single dev agent workflow?▼

Yes, you can use this requirements decomposition approach for a single dev agent workflow because it specifically sizes each user story to be independently completable by one developer entity.

Why must story creation follow a step-file workflow with validation gating?▼

Story creation must follow a step-file workflow with validation gating to ensure template-based document generation correctly maps functional requirements to epics and enforces quality-focused output before proceeding.