skills.rest
ArchaonHW
ArchaonHWCOMMUNITY
Explore all skills by this author →
GitHub

bmad-create-epics-and-stories

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

Updated Mar 14, 2026
Search Tags:#requirements#acceptance criteria#epics#user stories#backlog#prd#agile planning
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-create-epics-and-stories-archaonhw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-create-epics-and-stories-archaonhw

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 functional requirements, non-functional requirements, and UX design requirements. - Collaborative Epic Design: Groups requirements into user-value-focused epics with an FR coverage map, enforcing dependency and file-churn rules. - Story Generation with Acceptance Criteria: Produces Given/When/Then acceptance criteria for each story, sized for a single dev agent, then validates full requirement coverage. - Use Case: After finishing a PRD and architecture spec for a new product, run this workflow to produce a complete epics.md with validated stories that a developer agent can implement directly. ## Quick Start Ask the agent 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 break a PRD into epics and user stories?▼

Extract all functional and non-functional requirements from the PRD, group them into epics organized by user value rather than technical layers, then write stories with Given/When/Then acceptance criteria. This workflow automates that process step by step with user approval gates.

What documents do I need before creating epics and stories?▼

You need a PRD containing functional and non-functional requirements and an Architecture document with technical decisions. A UX design document is optional but recommended, since UX requirements are extracted as first-class inputs for story creation.

How should acceptance criteria for user stories be written?▼

Write acceptance criteria in Given/When/Then format so each criterion is independently testable. Include preconditions, the user action, the expected outcome, and edge cases or error conditions, referencing the specific requirement the story fulfills.

Can stories within an epic depend on future stories?▼

No. Each story must be completable using only the output of previous stories in the sequence. The workflow explicitly validates that no story has forward dependencies and that each epic delivers standalone user value.

What are common mistakes when designing epics?▼

Common mistakes include organizing epics by technical layers like database or API setup, creating all database tables upfront, and splitting work that repeatedly modifies the same files into multiple epics. Epics should each deliver complete, independent user value.

Related Skills

Explore More Product & Management Skills→
deltatreedeltatree

bmad-create-epics-and-stories

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

Community
Advanced
deanpetersdeanpeters
6.4k

epic-breakdown-advisor

Break epics into user stories using the Humanizing Work methodology.

Community
Basic
macollins27macollins27

specify

Convert plain-English feature requests into technical specifications with user stories and test plans.

Community
Advanced
apacheapache
79

magpie-issue-backlog-stats

Analyze open issues and generate backlog health metrics with recommendations.

Official
Advanced