What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tickets often end up as horizontal layer slices that cannot be demoed, lack clear dependency ordering, or lose context when handed to an agent or teammate. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which other tickets block it, and publishes them to a local file structure or a real issue tracker. ## Core Features & Use Cases - Vertical slice breakdown: Each ticket cuts a complete path through schema, API, UI, and tests so it is demoable on its own and fits in a single context window. - Blocking edge declaration: Every ticket lists the tickets that must complete first, published as text references locally or native blocking links on GitHub, Linear, or similar trackers. - Wide refactor handling: Large mechanical changes are sequenced as expand-migrate-contract batches instead of forced vertical slices, keeping CI green between batches. - Use Case: After drafting a feature spec for a new checkout flow, run this Skill to produce a numbered set of dependency-ordered tickets, review the breakdown interactively, then publish them as GitHub issues labeled ready-for-agent. ## Quick Start Ask the assistant to break the current plan or a referenced spec into tracer-bullet tickets with blocking dependencies and publish them to the configured tracker.
