skills.rest
HordRicJr
HordRicJrCOMMUNITY
Explore all skills by this author →
GitHub

bmad-create-epics-and-stories

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

6|Updated Aug 29, 2026
Search Tags:#requirements#acceptance criteria#epics#user stories#backlog#prd#agile planning
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-create-epics-and-stories-hordricjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill bmad-create-epics-and-stories-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a PRD and architecture document into a developer-ready 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 decomposition so every requirement maps to an implementable story. ## Core Features & Use Cases - Requirements Extraction: Scans PRD, Architecture, and UX design documents to inventory functional requirements, non-functional requirements, and UX design requirements. - Epic Design with Coverage Mapping: Groups requirements into user-value-focused epics and produces an FR coverage map so nothing is dropped. - Story Generation with Acceptance Criteria: Creates 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 product, run this Skill to produce a complete epics.md with validated stories ready to hand to a developer agent. ## 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 and architecture documents, then run the workflow. It extracts all functional and non-functional requirements, groups them into user-value-focused epics, and generates stories with testable acceptance criteria for each epic.

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 acceptance criteria written for each story?▼

Acceptance criteria use the Given/When/Then format, with each criterion independently testable. Stories are sized for a single dev agent and must not depend on future stories within the same epic.

Does the workflow check that all requirements are covered?▼

Yes. A final validation step verifies every FR maps to at least one story, checks epic independence, validates story dependency ordering, and confirms UX design requirements are covered before completing.

Can I customize the epic and story workflow behavior?▼

Yes. A customize.toml file supports activation step overrides, persistent facts loaded from project files, and an on_complete hook, merged with team and user-level override files.

Related Skills

Explore More Product & Management Skills→
0xHoneyJar0xHoneyJar
1

architect

Extract functional and non-functional requirements from a PRD into a Software Design Document.

Official
Advanced
bmad-code-orgbmad-code-org
52.5k

bmad-create-story

Generates comprehensive developer story files from epics, architecture, and sprint status artifacts.

Official
Advanced
Lia-CreativeLia-Creative
1

story-writer

Write user stories with Dan North narrative format and numbered Given/When/Then acceptance criteria.

Official
Intermediate
MichaelSolatiMichaelSolati

to-prd

Synthesize conversation and codebase context into structured PRDs and publish them to the issue tracker.

Community
Intermediate