skills.rest
paulingham
paulinghamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

epic-breakdown

Decompose epics into deployable stories with acceptance criteria and estimates.

1|Updated Mar 15, 2026
Search Tags:#planning#agile#estimation#delivery#epic#acceptance-criteria#story-decomposition
One-click install
npx skills add https://github.com/paulingham/.claude --skill epic-breakdown-paulingham
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epic-breakdown
Source: https://github.com/paulingham/.claude/tree/main/skills/epic-breakdown
Command: npx skills add https://github.com/paulingham/.claude --skill epic-breakdown-paulingham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose an epic into deployable stories with clear acceptance criteria and estimates to guide design, sizing, and delivery.

Core Features & Use Cases

  • Vertical-slice decomposition that yields end-to-end stories with explicit acceptance criteria and testable outcomes.
  • Estimation guidance and sizing notes to align stakeholders on effort and risk.
  • Structured output including priorities, dependencies, and optional alternatives to inform planning and parallel work.

Quick Start

Prepare an epic description and return a prioritized set of stories, each with acceptance criteria and 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 break down an epic into actionable user stories?▼

Epic decomposition involves breaking large features into vertical slices to produce deployable stories. Each story receives structured acceptance criteria, estimates, priorities, and dependencies to guide sprint planning and delivery.

What is vertical slice decomposition in agile planning?▼

Vertical slice decomposition is an agile planning technique that breaks epics into end-to-end stories. This ensures each story delivers testable outcomes across architecture and engineering teams, rather than splitting work by horizontal technical layers.

How do I estimate effort and risk for agile story decomposition?▼

Estimating effort and risk for story decomposition requires sizing notes and estimation guidance applied to each vertical slice. This aligns stakeholders on the specific effort and risk associated with delivering each deployable story.

Can I get acceptance criteria and priorities when decomposing epics for sprint planning?▼

Yes, decomposing epics for sprint planning yields a structured set of deployable stories. Each story includes explicit acceptance criteria, priorities, dependencies, and optional alternatives to inform parallel work and delivery.

What is the best way to structure story dependencies and alternatives for architecture and engineering teams?▼

The best way to structure story dependencies is to produce a prioritized set of deployable stories with explicit dependencies and optional alternatives. This informs planning and enables parallel work across architecture and engineering teams.

Related Skills

Explore More Product & Management Skills→
loianeloiane
50

epic-slicing-planning

Plan Epic-level architecture and vertical-slice roadmaps for large features.

Community
Advanced
vuralserhat86vuralserhat86
43

project_manager

Manage agile and scrum project lifecycles with backlog creation and sprint planning.

Community
Intermediate
markus41markus41
1

scrum

Facilitate Scrum ceremonies and manage sprint backlog with agile estimation.

Community
Basic
wtthorntonwtthornton
4

planner

Creates user stories, epics, and tasks with Fibonacci point estimates.

Community
Advanced