skills.rest
GenEducation
GenEducationOFFICIAL
Explore all skills by this author →
GitHub

bmad-create-epics-and-stories

Break product requirements into validated epics and user stories with acceptance criteria.

Updated Mar 30, 2026
Search Tags:#architecture#requirements#epics#user stories#backlog#prd#ux
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-create-epics-and-stories-geneducation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-epics-and-stories
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-create-epics-and-stories
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-create-epics-and-stories-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered product, architecture, and UX inputs into a structured epic and story plan, reducing ambiguity and speeding up handoff to development.

Core Features & Use Cases

  • Requirements extraction: Pull functional, non-functional, and technical requirements from PRD, architecture, and UX documents.
  • Epic design: Group requirements into user-value-focused epics with clear coverage mapping.
  • Story generation: Produce implementation-ready user stories with testable acceptance criteria.
  • Use case: A product team has a PRD, an architecture note, and a UX spec for a new feature and needs a complete development-ready backlog that is validated for coverage and sequencing.

Quick Start

Ask this Skill to analyze your requirements documents and produce a validated epic and story breakdown for development.

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 a PRD into epics and user stories?▼

To extract requirements from architecture notes and UX specs, you pull functional, non-functional, and technical inputs from these documents and map them to deliverable work scopes for structured backlog organization.

What is the best way to organize a development-ready backlog from scattered product inputs?▼

Generating user stories with clear acceptance criteria from requirements produces implementation-ready backlog items validated for complete epic coverage and sequenced for development delivery.

Can I map architecture and UX requirements to deliverable work items?▼

Mapping architecture and UX requirements to deliverable work items requires no dependencies, allowing you to directly process PRD, architecture, and UX inputs to produce structured documentation for developer handoff.

How do I ensure epic coverage when creating user stories from requirements?▼

Ensuring epic coverage when creating user stories involves grouping extracted requirements into user-value-focused epics and validating that every generated story maps clearly to these epic scopes.

What's the best way to sequence user stories for development handoff?▼

Sequencing user stories for development handoff requires mapping requirements to deliverable work, organizing stories by user-value-driven scopes, and producing structured documentation validated for coverage.

Related Skills

Explore More Product & Management Skills→
jaydubya818jaydubya818

bmad-create-epics-and-stories

Decompose PRD and Architecture requirements into mapped epics and stories.

Community
Advanced
blazefluzblazefluz

Work Intake Manager

Convert natural language requests into structured user stories, epics, and bug reports.

Community
Advanced
vndkubivndkubi

estimate-effort

Estimate development effort for backlog items with story points and confidence.

Community
Advanced
curdxcurdx
4

bmad-create-epics-and-stories

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

Community
Advanced