skills.rest
mol4
mol4COMMUNITY
Explore all skills by this author →
GitHub

bmad-create-epics-and-stories

Break product requirements into validated epics and user stories.

1|Updated Mar 31, 2026
Search Tags:#requirements#acceptance criteria#epics#user stories#product planning#bmad
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-create-epics-and-stories-mol4
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-create-epics-and-stories-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns product requirements into a structured epic and story breakdown, removing the manual effort of decomposing scope, tracking coverage, and preparing development-ready work items.

Core Features & Use Cases

  • Requirements Extraction: Reads PRD, architecture, and UX documents to capture functional, non-functional, and technical requirements.
  • Epic Design: Groups requirements into user-value-focused epics with clear coverage mapping.
  • Story Generation: Produces implementation-ready user stories with testable acceptance criteria.
  • Validation Workflow: Checks completeness, dependency flow, and document consistency before release.
  • Use Case: A product team can feed in planning artifacts for a new feature and receive a complete, reviewable backlog structure ready for development.

Quick Start

Ask this skill to analyze the project planning documents and create the epics-and-stories breakdown for the repository.

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 turn a PRD into ready-to-build epics and user stories?▼

To turn a PRD into epics and user stories, you extract functional and technical requirements from planning documents, group them into user-value-focused epics, and generate implementation-ready stories with testable acceptance criteria.

What is the best way to write acceptance criteria for user stories from product requirements?▼

Writing acceptance criteria for user stories involves a stepwise requirement extraction process from PRD and UX documents, followed by mapping those requirements to stories to ensure testable coverage and document consistency.

Does this epics and stories generation workflow work with markdown planning artifacts?▼

Yes, this workflow applies to repositories that contain PRDs, architecture decisions, and UX specifications stored specifically as markdown planning artifacts to extract and validate requirements.

How do I validate coverage and dependency flow when breaking down product requirements into epics?▼

Validating coverage and dependency flow requires a final validation workflow that checks completeness, dependency mapping, and document consistency across the extracted requirements, generated epics, and user stories.

Related Skills

Explore More Product & Management Skills→
deltatreedeltatree

bmad-create-epics-and-stories

Decompose product requirements and UX designs into epics and user stories with acceptance criteria.

Community
Advanced
EvanPluchartEvanPluchart
2

sprint-planner

Transform finalized feature plans into sprint epics and stories with progress tracking.

Community
Intermediate
yukikmyukikm

prd-writing

Generate a Product Requirements Document draft from initial requirements.

Community
Advanced
AbsolutelySkilledAbsolutelySkilled
207

user-stories

Generate user stories and acceptance criteria using INVEST and Given/When/Then templates.

Official
Advanced