user-story-splitting

Split oversized user stories into smaller deliverables using eight splitting patterns.

Updated Aug 18, 2024
One-click install
npx skills add https://github.com/ch-m-n/dotfile --skill user-story-splitting-ch-m-n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-story-splitting
Source: https://github.com/ch-m-n/dotfile/tree/main/opencode/skills/user-story-splitting
Command: npx skills add https://github.com/ch-m-n/dotfile --skill user-story-splitting-ch-m-n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams break down oversized stories or epics that stall estimation, sequencing, or release readiness into smaller, independently deliverable work items while preserving user value and flow.

Core Features & Use Cases

  • Framework of eight splitting patterns that guides decomposition across workflow steps, business rules, data variations, acceptance criteria, technical effort, dependencies, DevOps, and discovery experiments.
  • Validation checklist ensures each split story delivers value, can be developed and tested independently, and stays sprint-sized, guarding against horizontal slicing or meaningless partitions.
  • Use case: When a backlog item spans several personas, workflows, or acceptance criteria, follow the template to choose the right split pattern and craft user stories with clear use cases and acceptance tests.

Quick Start

Ask the skill to split your epic by applying workflow steps or acceptance criteria patterns until each story delivers focused user value.

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 epics into sprint-ready user stories?

To split epics into sprint-ready user stories, apply pattern-based decomposition across workflow steps, business rules, and acceptance criteria until each story delivers focused user value and fits within a single sprint.

What is pattern-based user story splitting?

Pattern-based user story splitting is a decomposition method using eight patterns—workflow steps, business rules, data variations, and technical effort—to break oversized epics into independent, testable deliverables.

When should I decompose an epic in an agile backlog?

Decompose an epic when a backlog item exceeds sprint capacity, bundles multiple workflows, or contains several acceptance criteria that block independent development, testing, or delivery progress.

How do I validate split user stories for independent delivery?

Validate split user stories using a checklist to ensure each item delivers standalone value, can be developed and tested independently, and avoids horizontal slicing or meaningless partitions.

Does pattern-based splitting work for stories with multiple personas?

Yes, pattern-based splitting handles stories spanning multiple personas by applying decomposition patterns to separate workflows and acceptance criteria, ensuring each split story maintains clear use cases and independent delivery.

What are the limitations of user story splitting patterns?

User story splitting patterns require strict validation to avoid horizontal slicing or meaningless partitions, and may need multiple pattern applications before stories achieve true independent development and sprint-sized delivery.