breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

2|2|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill breakdown-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakdown-epic
Source: https://github.com/adolfoaranaes12/BMAD-ENHANCED/tree/main/.claude/skills/breakdown-epic
Command: npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill breakdown-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires epic-analysis, and includes references (resource) and templates (resource) components.

What problem does it solve?

This Skill breaks down epics into implementable user stories with acceptance criteria, estimates, dependencies, and sprint groupings.

Core Features & Use Cases

  • Epic analysis into major components
  • Story creation with clear AC and estimates
  • Dependency mapping and sprint grouping suggestions
  • Epic-file generation and traceability

Quick Start

Break down an epic into stories and generate sprint-ready backlog.

Frequently Asked Questions about breakdown-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a large epic into user stories with estimates?

Epic breakdown transforms large epics into implementable user stories by analyzing requirements, generating acceptance criteria, assigning story points, and mapping dependencies. The Skill produces structured stories ready for sprint planning and backlog prioritization.

Can I organize stories into sprint groups when breaking down epics?

Yes. The Skill creates sprint groupings alongside story generation, organizing stories by dependencies and complexity to produce a sprint-ready backlog with recommended sequencing and point allocations across sprints.

What dependencies does epic breakdown rely on?

Epic breakdown depends on epic-analysis, which extracts core components and requirements from epic descriptions. This prerequisite analysis feeds the story creation pipeline to ensure accurate decomposition and dependency mapping.

Do I need a defined tech stack to break down epics effectively?

A tech stack is optional but recommended. Providing your technology stack enables the Skill to generate technically-informed stories with platform-specific acceptance criteria and more accurate dependency graphs and estimates.

What outputs does epic breakdown produce for sprint planning?

Epic breakdown generates user story files with acceptance criteria and estimates, an epic traceability file, total story points, story count, sprint count, and dependency graphs—all formatted for immediate backlog import and sprint assignment.

Related Skills