skills.rest
qa-aman
qa-amanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

epic-breakdown

Decompose approved epics into sprint-ready sub-epics with story-point estimates.

19|3|Updated Feb 28, 2026
Search Tags:#agile#decomposition#epic#sprint-planning#story-points#sub-epics
One-click install
npx skills add https://github.com/qa-aman/claude-skills --skill epic-breakdown-qa-aman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-breakdown
Source: https://github.com/qa-aman/claude-skills/tree/main/skills/by-role/pm/epic-breakdown
Command: npx skills add https://github.com/qa-aman/claude-skills --skill epic-breakdown-qa-aman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose large epics into sprint-ready sub-epics using a structured 9-pattern approach to enable reliable sprint planning and handoff.

Core Features & Use Cases

  • Break down a feature epic into sized sub-epics with clear scope and story points.
  • Map dependencies between sub-epics and suggest sprint allocations.
  • Support engineering handoff with concrete deliverables and acceptance criteria.

Quick Start

Provide a spec directory to the Epic Breakdown skill and generate a set of sub-epics with estimates ready for sprint planning.

Frequently Asked Questions about epic-breakdown

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

FAQPage Schema
How do I decompose large epics into sprint-ready sub-epics?▼

Epic decomposition breaks large epics into sprint-ready sub-epics using a 9-pattern approach. It generates sized sub-epics with story-point estimates and dependency maps to enable reliable sprint allocation and engineering handoff.

When do I need to break down an approved spec into estimable work items?▼

Breaking down an approved spec into estimable work items is needed when preparing for engineering handoff and sprint planning. It ensures large features are segmented into sub-epics with clear scope, concrete deliverables, and acceptance criteria.

What is the best way to estimate story points for sub-epics during sprint planning?▼

Estimating story points for sub-epics during sprint planning is handled by applying 9 decomposition patterns to an approved spec. This yields sized sub-epics with story-point estimates and mapped dependencies for strategic sprint allocation.

Can I map dependencies between sub-epics for strategic sprint allocation?▼

Yes, you can map dependencies between sub-epics for strategic sprint allocation. The decomposition process outputs a dependency map alongside sized sub-epics with story points to guide sprint planning and engineering handoff.

Does epic decomposition support engineering handoff with acceptance criteria?▼

Epic decomposition supports engineering handoff by generating concrete deliverables and acceptance criteria for each sub-epic. This structured breakdown ensures engineering teams receive sized, sprint-ready work items with clear scope.

Related Skills

Explore More Product & Management Skills→
burningddolburningddol

speckit-checklist

Generate domain-aligned requirement checklists from spec-kit feature files.

Community
Advanced
cwinvestmentscwinvestments
412

user-story-generator

Generate prioritized user stories with acceptance criteria and story points in CSV format.

Community
Advanced
hongmaple0820hongmaple0820
9

agile-product-owner

Convert requirements into INVEST-aligned user stories and backlog items.

Community
Advanced
deanpetersdeanpeters
6.4k

epic-breakdown-advisor

Break epics into user stories using the Humanizing Work methodology.

Community
Basic