What problem does it solve? When a ticket is too large for a single slice, the approved plan alone lacks the user-facing behaviour boundaries and testing seams needed to cut it into clean slices. This Skill transforms the existing planner output into a compact slice-ready spec without re-interviewing anyone or re-exploring the codebase. ## Core Features & Use Cases - Slice-ready spec generation: Reads planner.md, context-gatherer.md, and ticket-analyzer.md handoffs and writes a slice-spec.md containing the problem, solution, behaviours, and out-of-scope items. - Testing seam identification: Maps each behaviour to the produce/verify step, integration entry point, or /test-ticket step that proves it, flagging shared seams that block clean slicing. - Behaviour boundary definition: Expresses each behaviour as a user story grouped by unit, giving /to-tickets natural lines to slice along. - Use Case: During the /start-ticket DECOMPOSE path, after the planner sets slice-count > 1 and the plan is approved, run this Skill to produce the spec that /to-tickets consumes to split a large ticket into slices. ## Quick Start Run the to-spec skill on the approved planner.md handoff for the current ticket to generate the slice-ready spec before running /to-tickets.
