Break down epics into user stories with Humanizing Work split patterns. Use when a backlog item is too large to estimate, sequence, or deliver safely.
Purpose Guide product managers through breaking down epics into user stories using Richard Lawrence's complete Humanizing Work methodology—a systematic, flowchart-driven approach that applies 9 splitting patterns sequentially. Use this to identify which pattern applies, split while preserving user value, and evaluate splits based on what they reveal about low-value work you can eliminate. This ensures vertical slicing (end-to-end value) rather than horizontal slicing (technical layers). This is not arbitrary slicing—it's a proven, methodical process that starts with validation, walks through patterns in order, and evaluates results strategically. Key Concepts Core Principles: Vertical Slices Preserve Value A user story is "a description of a change in system behavior from the perspective of a user." Splitting must maintain vertical slices—work that touches multiple architectural layers and delivers observable user value—not horizontal slices addressing single components (e.g., "front-end story" + "back-end story"). The Three-Step Process Pre-Split Validation: Check if story satisfies INVEST criteria (except "Small") Apply Splitting Patterns: Work through 9 patterns sequentially until one fits Evaluate Splits: Choose the split that reveals low-value work or produces equal-sized stories
don't have the plugin yet? install it then click "run inline in claude" again.