bmad-create-epics-and-stories

Name: bmad-create-epics-and-stories
Availability: InStock
Author: ThuanTan2060

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

Updated May 17, 2026

Search Tags:#acceptance criteria #epics #product strategy #user stories #BMAD planning #requirements decomposition

Ready to run

npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-create-epics-and-stories-thuantan2060

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps teams decompose PRD and architecture inputs into a complete, developer-ready epic and user story breakdown with clear acceptance criteria, reducing ambiguity and rework.

Core Features & Use Cases

Requirement extraction and structuring: Extract functional requirements (FRs), non-functional requirements (NFRs), and architecture-driven constraints into a single planning artifact.
Epic structuring by user value: Produce a standalone epic list organized around user outcomes, with explicit FR coverage mapping.
Story generation with testable acceptance criteria: Generate user stories sized for single-agent completion and enforce “no forward dependencies” within epics.

Quick Start

Ask the workflow to create the epics and stories list for your PRD, Architecture, and (if available) UX Design documents so the developer can start implementing immediately.

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 product requirements into epics and user stories?▼

To break down product requirements into epics and user stories, you extract functional and non-functional constraints from your PRD and architecture documents to generate a user-value-first epic plan with explicit acceptance criteria. This ensures every story is standalone and developer-ready.

How do I write user stories with acceptance criteria for sequential development?▼

Writing user stories with acceptance criteria for sequential development involves structuring stories sized for single-agent completion and enforcing a “no forward dependencies” constraint within each epic. This template compliance guarantees developers can implement tasks immediately without waiting on future requirements.

Can I integrate UX design requirements into my epic and story breakdown?▼

Yes, you can integrate UX design requirements into your epic and story breakdown by feeding your UX Design documents alongside your PRD and architecture inputs. The workflow extracts these constraints to ensure the generated user stories align with both functional and design requirements.

What is the best way to map functional requirements to epics?▼

The best way to map functional requirements to epics is to structure your epic list around user outcomes while applying explicit FR coverage mapping. This approach transforms raw product strategy into a standalone epic plan that directly ties each user value to a specific functional requirement.

Why do my user stories have forward dependencies that block developer implementation?▼

User stories have forward dependencies when the requirements decomposition fails to enforce a “no future dependencies” constraint within epics. Generating standalone stories sized for single-agent completion eliminates these blockers, ensuring developer-ready output for sequential planning.

Do I need a complete architecture document to generate build-ready user stories?▼

You need a PRD and architecture document to generate build-ready user stories, as these provide the functional and non-functional requirements required for extraction. An optional UX Design document can also be supplied to further refine the developer-ready output.