user-story-splitting

What problem does it solve?

Break down oversized user stories, epics, or features into smaller, independently deliverable stories to reduce risk, improve feedback cycles, and maintain momentum in agile teams.

Core Features & Use Cases

• Structured splitting: Apply one of eight patterns (Workflow steps, Business rule variations, Data variations, Acceptance criteria complexity, Major effort, External dependencies, DevOps steps, Tiny Acts of Discovery) to decompose work without losing user value.
• Templates and guidance: Use provided templates (e.g., template.md) to generate complete, testable splits aligned with your backlog.
• Use Case: When an epic spans multiple sprints, split it into smaller stories that can be independently implemented and validated.

Quick Start

Start with a large story, reference the splitting templates, identify the first applicable pattern, and craft 2–3 smaller stories with clear acceptance criteria.