epic-breakdown-advisor

Break epics into user stories using Humanizing Work splitting patterns.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/omeragaakbas/zoyare --skill epic-breakdown-advisor-omeragaakbas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-breakdown-advisor
Source: https://github.com/omeragaakbas/zoyare/tree/main/.claude/skills/epic-breakdown-advisor
Command: npx skills add https://github.com/omeragaakbas/zoyare --skill epic-breakdown-advisor-omeragaakbas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break epics down into actionable, end-to-end user stories using the Humanizing Work splitting patterns to prevent arbitrary slicing and preserve customer value.

Core Features & Use Cases

  • 9 patterns applied sequentially to break epics into runnable stories
  • Ensures vertical slicing that delivers observable user value
  • Guides INVEST alignment and evaluation to prune low-value work and balance story sizes

Quick Start

Provide your epic context and run through the INVEST checks, apply the first matching pattern, and evaluate the split for value and size.

Frequently Asked Questions about epic-breakdown-advisor

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

FAQPage Schema
How do I break epics into actionable user stories for sprint planning?

To break epics into actionable user stories, apply the Humanizing Work splitting patterns sequentially. This ensures vertical slicing that delivers observable user value and produces runnable stories with clear acceptance criteria for backlog refinement.

What is the INVEST validation step for epic breakdown?

INVEST validation is a pre-split check applied to epics before decomposition. It enforces alignment with Independent, Negotiable, Valuable, Estimable, Small, and Testable criteria to ensure the resulting user stories are safe to estimate and deliver.

How do I use vertical slicing to split large product backlog items?

Vertical slicing is applied through nine sequential patterns to split large backlog items. This approach preserves customer value by ensuring each resulting story delivers end-to-end observable functionality rather than arbitrary horizontal layers.

When should I split epics during product roadmap decomposition?

You should split epics during roadmap decomposition when items become too large to estimate or deliver safely. The process prunes low-value work and balances story sizes to support safe sprint planning and backlog refinement.

What is the best way to prevent arbitrary story splitting in product management?

The best way to prevent arbitrary story splitting is to enforce sequential pattern application from the Humanizing Work framework. This method evaluates each split for value and size, ensuring observable user value is preserved across the breakdown.

Does epic breakdown work for evaluating low-value work in a backlog?

Yes, epic breakdown includes an evaluation phase that identifies and prunes low-value work. By applying INVEST checks and splitting patterns sequentially, it balances story sizes and produces a clear breakdown focused on high-value delivery.