What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tickets end up as horizontal layer slices, dependencies are implicit, and nothing is sized to fit a single working session. This Skill decomposes work into vertical tracer-bullet tickets, each declaring exactly which tickets block it, and publishes them to your configured issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: Each ticket cuts a complete path through schema, API, UI, and tests so it is demoable on its own and fits in one fresh context window. - Blocking edge modeling: Every ticket declares its blockers, with wide refactors handled via expand-migrate-contract sequencing to keep CI green. - Flexible publishing: Writes one file per ticket under .scratch/<feature-slug>/issues/ locally, or creates real issues with native blocking links and a ready-for-agent label on trackers like GitHub or Linear. - Use Case: After drafting a feature spec in conversation, ask for a ticket breakdown; review the proposed numbered list with blocking edges, approve it, and get tracker-ready issues ordered so blockers land first. ## Quick Start Ask the agent to break the current plan or spec into tracer-bullet tickets with blocking edges and publish them to the configured tracker.
