skills.rest
locus-taxy
locus-taxyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

user-story-splitting

Decomposes large user stories and epics into smaller, independently deliverable stories using eight splitting patterns.

Updated Aug 27, 2026
Search Tags:#agile#estimation#split#backlog#acceptance-criteria#user-story#story-splitting
One-click install
npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill user-story-splitting-locus-taxy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-story-splitting
Source: https://github.com/locus-taxy/locus-SD-toolkit/tree/main/skills/user-story-splitting
Command: npx skills add https://github.com/locus-taxy/locus-SD-toolkit --skill user-story-splitting-locus-taxy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break down large user stories or epics into smaller, independently deliverable stories to improve estimation, risk management, feedback cycles, and flow.

Core Features & Use Cases

  • Framework-based decomposition using eight patterns to split stories.
  • Ensures each split delivers user value and can be developed and tested independently.
  • Use Case: Break a large epic into deliverable increments that fit into sprint planning and release cycles.

Quick Start

Identify the original story in user-story format, then apply the eight patterns in order to generate multiple independent, value-driven splits.

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 user stories into smaller deliverable chunks?▼

Split large user stories by applying eight decomposition patterns sequentially, including workflow steps, business rule variations, and data variations, to generate independent, value-driven stories that fit within a single sprint.

What is the best way to break down an epic with multiple acceptance criteria?▼

Breaking down an epic with multiple acceptance criteria uses a deterministic reduction process based on acceptance criteria complexity, ensuring each split story delivers user value and can be developed and tested independently.

When should I split user stories in an agile backlog?▼

Split user stories in an agile backlog when work items exceed a single sprint or involve external dependencies, data variations, or complex business rules, ensuring faster feedback cycles and improved estimation accuracy.

Can I use story splitting patterns for work items with external dependencies?▼

Story splitting patterns explicitly handle work items with external dependencies by isolating those dependencies into independently deliverable stories, accelerating delivery flow and managing risk effectively.

What are the eight patterns for decomposing agile epics?▼

The eight patterns for decomposing agile epics are workflow steps, business rule variations, data variations, acceptance criteria complexity, major effort, external dependencies, DevOps steps, and tiny acts of discovery.

Does splitting a user story require a specific format for the original work item?▼

Splitting a user story requires identifying the original work item in a standard user-story format before applying the eight patterns to generate structured outputs in a reusable template.

Related Skills

Explore More Product & Management Skills→
petrSimonidesXartpetrSimonidesXart

generate-stories

Translate Epics into user stories with acceptance criteria and backlog entries.

Community
Advanced
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
yuyuxinliyuyuxinli
1

user-story-splitting

Split large user stories into smaller deliverable stories using eight patterns.

Official
Intermediate
MaxKlat29MaxKlat29

epic-breakdown-advisor

Guides users through systematic decomposition of project epics into user stories.

Community
Intermediate