breakdown-epic

name	breakdown-epic
description	Break down epics into implementable user stories with acceptance criteria, estimates, dependencies, and sprint groupings. This skill should be used for epic planning and backlog grooming.
acceptance	[{"components_identified":"Major components and sub-features identified from epic"},{"stories_created":"User stories created in proper format with acceptance criteria"},{"estimates_provided":"Story points estimated using complexity/effort/risk"},{"dependencies_mapped":"Dependencies between stories identified and documented"},{"sprints_suggested":"Sprint groupings suggested based on dependencies and priorities"}]
inputs	{"epic_description":{"type":"string","required":true,"description":"Epic or feature description to break down"},"tech_stack":{"type":"array","required":false,"description":"Technology stack for technical considerations"}}
outputs	{"story_files":{"type":"array","description":"List of generated story file paths"},"epic_file":{"type":"string","description":"Path to generated epic summary file"},"total_points":{"type":"number","description":"Total story points across all stories"},"story_count":{"type":"number","description":"Number of stories created"},"sprint_count":{"type":"number","description":"Suggested number of sprints"}}
telemetry	{"emit":"skill.breakdown-epic.completed","track":["story_count","total_points","sprint_count","priority_distribution","dependency_count","duration_ms"]}

Breakdown Epic Skill

Purpose

Transform high-level epics or features into detailed, actionable user stories ready for sprint planning and implementation.

Core Capabilities:

• Epic scope analysis and component identification
• User story creation (As a... I want... So that...)
• Story point estimation (complexity/effort/risk)
• Dependency mapping between stories
• Sprint grouping suggestions
• Story and epic file generation

Prerequisites

• Configuration file (.claude/config.yaml) with planning settings
• Epic description (20+ words minimum)
• Story point scale defined (default: Fibonacci 1,2,3,5,8,13,21)

---

Workflow

Step 0: Load Configuration and Epic Description

Action: Load configuration and parse epic requirements.

Load config: Read .claude/config.yaml for planning settings (storiesLocation, epicsLocation, defaultVelocity, storyPointScale, techStack)

Get epic description: From user input (20+ words minimum), parse scope, business goals, technical requirements

Prepare directories: Create stories and epics directories

See: references/templates.md#configuration-format and #step-0-configuration-loading for details

Halt if:

• Configuration missing
• Epic description <20 words (too vague)
• Cannot create directories

See: references/epic-analysis-guide.md for scope analysis

---

Step 1: Analyze Epic Scope

Action: Break down epic into major components and sub-features.

Identify components:

1. Core Features - What functionality is needed?
2. User Types - Who will use this?
3. Technical Requirements - What tech/integrations?
4. Security Requirements - What needs protection?
5. Non-Functional Requirements - Performance, scalability, etc.

Output: Epic analysis with major components, sub-features, user types, technical/security requirements, NFRs

See: for complete analysis format