What problem does it solve? Oversized epics and XXL stories cannot be estimated, planned, or delivered within a single iteration, and teams lack a consistent method to split them into valuable, testable slices while preserving traceability. ## Core Features & Use Cases - Split Gate Enforcement: Treats XXL sizing as a mandatory split gate and re-splits any slice that remains XXL before estimation. - Five Splitting Patterns: Splits by workflow steps, business rules, data variations, CRUD operations, or interfaces, keeping every slice INVEST-compliant. - Traceability Preservation: Links every slice to its parent epic or story, carries acceptance criteria down to the owning slice, and declares cross-slice dependencies. - Use Case: During backlog refinement, a BA finds an XXL story spanning three personas; the Skill produces a slice table (ID, title, parent, value, dependencies, size) and persists each slice as a local task via sf setup-agents task create. ## Quick Start Ask the assistant to decompose the XXL story about checkout into independently deliverable slices and record each one in the local backlog.
