What problem does it solve? Large stories, epics, and backlog items are too big to deliver, test, and learn from in small batches, and naive decomposition produces technical component tasks instead of independently valuable user-facing slices. ## Core Features & Use Cases - Vertical Slice Decomposition: Reframe broad requirements into child stories that each deliver a complete user-visible capability through the real production path, avoiding component or layer splits. - Pattern Catalog: Apply SPIDR, Hamburger Method, Humanizing Work patterns, and Bill Wake's twenty splitting approaches when a story resists simple decomposition. - Quality Validation: Check every child story against INVEST criteria and a red-flag checklist before handing off to implementation planning. - Use Case: Given an epic like "build online banking portal," reframe it into capabilities such as "customers can pay bills," then produce a first walking-skeleton slice plus a table of follow-up slices with acceptance examples and release constraints. ## Quick Start Ask the assistant to split a large epic or backlog item into small end-to-end stories using the story-splitting skill.
