What problem does it solve? Teams often jump from product vision straight to backlog items without properly scoping vertical slices, resulting in oversized work items, missing smoke tests, and unclear dependencies. This Skill structures the slice discovery conversation so every slice is verifiable and sprint-sized before PBIs are created. ## Core Features & Use Cases - Four slice types: Supports Functional, Enabler, Spike, and Foundational slices, each with a tailored interview and document template. - Context-aware interviews: Reads the PRD, product journey, and architecture docs to pre-populate questions about journey stages, entities, and business rules instead of asking from scratch. - Quality gates: Blocks documentation when a smoke test, spike deliverable, or foundational Definition of Done is missing, and pushes back when users describe technical layers instead of slices. - Use Case: After completing your product journey map, run this Skill to discover S1 (a foundational setup slice) and S2 (a functional login slice), producing traceable files in docs/05_scrum/discovery/ ready for backlog creation. ## Quick Start Ask the assistant to run slice discovery for the next slice of your project using the existing product journey and PRD documents.
