bmad-create-epics-and-stories

Transform product requirement documents into structured epics and user stories.

Updated May 5, 2026
One-click install
npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-create-epics-and-stories-devalexanderdaza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/devalexanderdaza/bmad-any/tree/main/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-create-epics-and-stories-devalexanderdaza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of decomposing product requirement documents (PRDs), architecture specifications, and UX design docs into structured, dev-ready epics and user stories, ensuring no requirements are missed and all work is aligned to user value.

Core Features & Use Cases

  • Comprehensive Requirement Extraction: Automatically pulls functional, non-functional, and UX requirements from PRDs, architecture docs, and UX specifications to create a complete requirements inventory.
  • User-Value-Focused Epic Design: Guides collaborative epic creation that groups requirements by user outcome, with built-in checks to ensure each epic is standalone and deliverable independently.
  • Testable Story Generation: Breaks each epic into appropriately sized user stories with clear Given/When/Then acceptance criteria, sized for single developer completion and fully traceable to original requirements. Use case: A product team with a finalized PRD and architecture document can use this Skill to generate a complete, prioritized backlog of epics and stories ready for development sprint planning.

Quick Start

Use the bmad-create-epics-and-stories skill to transform your project's PRD, architecture, and UX requirements into a complete, dev-ready backlog of epics and user stories.

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 product requirement document into epics and user stories?

Breaking down a product requirement document into epics and user stories involves extracting functional, non-functional, and UX requirements to create a complete, dev-ready backlog. This ensures comprehensive requirement coverage aligned to user value.

What is the best way to generate user stories with acceptance criteria from architecture specifications?

The best way to generate user stories with acceptance criteria from architecture specifications is to break epics into appropriately sized stories using clear Given/When/Then formats. This ensures stories are sized for single developer completion and fully traceable to original requirements.

Can I use my existing PRD and UX design docs to create a complete agile backlog?

Yes, you can use your existing PRD and UX design docs to create a complete agile backlog. The process pulls requirements from these documents to generate a prioritized list of standalone, independently deliverable epics and stories ready for sprint planning.

How are epics structured to ensure they deliver independent user value?

Epics are structured to deliver independent user value by grouping requirements by user outcome and applying built-in checks. This ensures each epic is standalone and can be delivered independently without relying on other work items.

Does this approach to requirement extraction ensure traceability back to the original documents?

Yes, this approach to requirement extraction ensures traceability by mapping generated stories directly back to original product requirement documents, architecture specifications, and UX design docs. This prevents missed requirements and maintains standardized story formatting.