user-story-splittinglisted

## Purpose Break down large user stories, epics, or features into smaller, independently deliverable stories using systematic splitting patterns. Use this to make work more manageable, reduce risk, enable faster feedback cycles, and maintain flow in agile development. This skill applies to user stories, epics, and any work that's too large to complete in a single sprint. This is not arbitrary slicing—it's strategic decomposition that preserves user value while reducing complexity. ## Key Concepts ### The Story Splitting Framework Based on Richard Lawrence and Peter Green's "Humanizing Work Guide to Splitting User Stories," the framework provides 8 systematic patterns for splitting work: 1. **Workflow steps:** Split along sequential steps in a user's journey 2. **Business rule variations:** Split by different rule scenarios (permissions, calculations, etc.) 3. **Data variations:** Split by different data types or inputs 4. **Acceptance criteria complexity:** Split when multiple "When" or "Then" statements exist 5. **Major effort:** Split by technical milestones or implementation phases 6. **External dependencies:** Split along dependency boundaries (APIs, third parties, etc.) 7. **DevOps steps:** Split by deployment or infrastructure requirements 8. **Tiny Acts of Discovery (TADs):** When none of the above apply, use small experiments to unpack unknowns ### Why Split Stories? - **Faster feedback:** Smaller stories ship sooner, allowing earlier validation - **Reduced risk: