bmad-create-epics-and-stories

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

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

Updated Mar 16, 2026

Search Tags:#workflow #requirements #product management #epics #user stories #backlog

Ready to run

npx skills add https://github.com/geekdesign27/travailleursisoles --skill bmad-create-epics-and-stories-geekdesign27

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/geekdesign27/travailleursisoles/tree/main/_bmad/bmm/workflows/3-solutioning/bmad-create-epics-and-stories
Command: npx skills add https://github.com/geekdesign27/travailleursisoles --skill bmad-create-epics-and-stories-geekdesign27

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of breaking down complex product requirements into manageable epics and user stories, ensuring clarity and actionable tasks for development teams.

Core Features & Use Cases

Requirements Decomposition: Transforms Product Requirements Documents (PRDs) and other inputs into structured epics and user stories.
Workflow Automation: Guides users through a disciplined, step-by-step process for creating a comprehensive backlog.
Use Case: When a new product feature is defined, use this Skill to automatically generate a detailed list of epics and user stories, complete with acceptance criteria, ready for development.

Quick Start

Use the bmad-create-epics-and-stories skill to create the epics and stories list.

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, this Skill automates the decomposition process by extracting inputs from PRDs, Architecture, and UX documents to organize value-driven epics and generate detailed stories with acceptance criteria.

What is the best way to generate a development backlog from a PRD?▼

Generating a development backlog from a PRD is best handled by using a defined workflow architecture to extract requirements, organize them into value-driven epics, and output detailed user stories complete with acceptance criteria.

Can I use architecture and UX documents as inputs for user story generation?▼

Yes, you can use architecture and UX documents for user story generation; the workflow specifically manages requirements extraction from PRDs, Architecture, and UX documents to ensure comprehensive backlog coverage.

Does the generated backlog include acceptance criteria for user stories?▼

Yes, the generated backlog includes acceptance criteria; the workflow ensures that detailed user stories are produced with acceptance criteria to provide actionable tasks for development teams.

How does the step-file execution model work for requirements decomposition?▼

The step-file execution model works for requirements decomposition by guiding users through a disciplined, automated, step-by-step process to create a comprehensive backlog from complex product requirements.