What problem does it solve? Turning a plan or specification into actionable work items often produces vague, overlapping, or unverifiable tickets. This Skill converts a source plan into bounded tickets with clear acceptance criteria and explicit blocking dependencies, avoiding duplicate or unverifiable work items. ## Core Features & Use Cases - Ticket Decomposition: Breaks a plan into tickets that each deliver a bounded, observable behavior across the necessary layers rather than unverifiable schema/API/UI splits. - Dependency Mapping: Declares only true blocking dependencies and identifies shared integration branches or coordinated deployment requirements for broad contract migrations. - Tracker Integration: Creates blockers first, uses returned identifiers for native dependency links, and verifies the resulting items when publication is authorized. - Use Case: Given an approved migration specification, produce a sequenced set of tickets where each one can be verified independently, with expand-migrate-contract ordering for contract changes. ## Quick Start Split the attached specification into independently verifiable tickets with acceptance criteria and blocking dependencies.
