bmad-create-epics-and-stories

Transform high-level requirements into epics and stories with acceptance criteria.

Updated Apr 25, 2026

Search Tags:#workflow #requirements #epics #decomposition #stories #product-management #acceptance-criteria

Ready to run

npx skills add https://github.com/ldk-hub/broke-shopping --skill bmad-create-epics-and-stories-ldk-hub

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams turn vague requirements into a concrete, testable set of epics and stories, aligning product strategy with engineering plan.

Core Features & Use Cases

Decomposes PRD, Architecture decisions, and UX considerations into standalone epics that deliver user value.
Creates actionable stories that are sized for single-developer work and include acceptance criteria.
Generates a FR/NFR mapping and a requirements coverage map to ensure complete traceability and auditability.

Quick Start

Identify the user problem and provide PRD/Architecture/UX inputs to begin the automated epic-and-story generation workflow.

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 high-level requirements into actionable epics and stories?▼

To break down high-level requirements, this skill decomposes PRD, architecture, and UX inputs into standalone epics that deliver user value, then generates actionable stories sized for a single developer. It also includes acceptance criteria for each story to ensure testability.

What is the best way to map functional requirements to user stories for traceability?▼

Mapping functional requirements to user stories for traceability is achieved by generating an FR and NFR coverage map alongside the epics and stories. This ensures every requirement is linked to a specific deliverable, providing complete auditability from product strategy to engineering plan.

How do I write acceptance criteria for decomposed product epics?▼

Writing acceptance criteria for decomposed product epics is handled automatically during the story generation process. The skill co-authors the output with the product owner, validating that each story includes specific acceptance criteria until explicit approval is obtained.

Can I use PRD and architecture documents to generate a complete backlog of stories?▼

Yes, you can use PRD and architecture documents to generate a complete backlog of stories. The skill transforms these high-level inputs into a concrete, testable set of epics and stories, mapping both functional and non-functional requirements to ensure full backlog coverage.

Does this approach validate generated stories with the product owner before finalizing?▼

Yes, this approach validates generated stories with the product owner before finalizing. The skill operates as a co-author, iterating on the epics and stories until the product owner provides explicit approval, ensuring the engineering plan aligns with product strategy.