user-story-splitting

Split large epics into smaller stories using structured splitting patterns.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill user-story-splitting-sicktastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-splitting
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/user-story-splitting
Command: npx skills add https://github.com/sicktastic/skill-issue --skill user-story-splitting-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns unwieldy epics and oversized user stories into manageable work by applying structured splitting patterns so estimation, sequencing, and independent release become possible.

Core Features & Use Cases

  • Eight splitting patterns provide a repeatable taxonomy that covers workflow steps, rule variations, data types, acceptance criteria, major effort milestones, dependencies, DevOps work, and discovery experiments.
  • Guided application walks product managers through identifying the original story, using the provided template, crafting split stories, and validating each split to ensure independent value delivery.
  • Use case: When a backlog item spans multiple personas, rules, or technical milestones, use this Skill to produce stories that are estimable, testable, and ready for sprint planning.

Quick Start

Use the user-story-splitting skill to analyze a bulky backlog item and apply the first applicable splitting pattern to produce sprint-ready stories.

Frequently Asked Questions about user-story-splitting

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

FAQPage Schema
How do I split large epics into sprint-ready user stories?

Splitting large epics into sprint-ready user stories requires evaluating workflow steps, rule variations, data cases, and dependencies to produce estimable, testable increments for backlog refinement and sprint planning.

What are the structured patterns for epic decomposition in agile?

Structured patterns for epic decomposition include eight categories: workflow steps, rule variations, data types, acceptance criteria complexity, major effort milestones, dependencies, DevOps needs, and discovery tasks.

When should I use story splitting patterns during backlog refinement?

Use story splitting patterns during backlog refinement when an oversized backlog item spans multiple personas, rules, or technical milestones, making it difficult to estimate, sequence, or independently release.

How do I validate that split user stories deliver independent value?

Validating split user stories for independent value involves a guided process that walks product managers through identifying the original story, crafting splits using templates, and verifying each increment delivers independent value.

Can I use story splitting for backlog items with complex acceptance criteria?

Yes, story splitting handles complex acceptance criteria by evaluating their complexity to determine splits, alongside other factors like workflow steps, data cases, dependencies, and major effort milestones.

Does story splitting work for backlog items requiring DevOps tasks?

Yes, story splitting evaluates DevOps needs as one of its eight patterns to break down oversized backlog items, ensuring technical infrastructure tasks are separated into manageable, estimable stories.