bmad-create-epics-and-stories

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill bmad-create-epics-and-stories-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/watchthelight/shatterfish --skill bmad-create-epics-and-stories-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD and architecture document into an actionable backlog is slow and error-prone: requirements get missed, epics get organized by technical layers instead of user value, and stories lack testable acceptance criteria. This Skill guides a structured, step-by-step workflow that extracts every requirement and converts it into an approved epic and story breakdown ready for developers. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX design documents to inventory all functional requirements, non-functional requirements, and UX design requirements. - User-Value Epic Design: Groups requirements into standalone epics organized by user outcomes, with an FR coverage map guaranteeing nothing is missed. - Story Generation with Acceptance Criteria: Produces Given/When/Then acceptance criteria for each story, sized for a single dev agent and free of forward dependencies. - Use Case: After finishing a PRD and architecture for a new web app, run this workflow to produce a complete epics.md with validated coverage that a developer agent can implement story by story. ## Quick Start Ask the AI to create the epics and stories list from your PRD and architecture documents.

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 epics and user stories?

Provide your PRD, architecture document, and optional UX design spec, then follow the guided workflow. It extracts all functional and non-functional requirements, groups them into user-value epics, and generates stories with Given/When/Then acceptance criteria.

What documents are required to create epics and stories?

A PRD containing functional and non-functional requirements and an architecture document are required. A UX design document is optional but recommended, since UX requirements are extracted as first-class inputs for story creation.

How are epics organized in this workflow?

Epics are organized by user value rather than technical layers, so each epic delivers complete standalone functionality. The workflow also checks for file churn across epics and recommends consolidation when multiple epics repeatedly modify the same components.

Does the workflow validate requirement coverage?

Yes, a final validation step checks that every FR maps to at least one story, stories have no forward dependencies, database entities are created only when needed, and each epic functions independently.

Can I customize the workflow behavior?

Yes, a customize.toml file supports team and user overrides for activation steps, persistent facts loaded from project files, and an on-complete hook, merged using structural rules.