What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is error-prone: slices end up horizontal, dependencies stay implicit, and tickets land in the tracker without clear ordering. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which tickets block it, and publishes them to the configured tracker. ## Core Features & Use Cases - Vertical slice drafting: Splits work into narrow but complete slices cutting through schema, API, UI, and tests, each demoable on its own and sized for a single context window. - Dependency modeling: Assigns blocking edges to every ticket and handles wide refactors via expand-contract sequencing with batched migrations. - Tracker publishing: Writes one file per ticket under .scratch/<feature-slug>/issues/ locally, or publishes native blocking issues to GitHub or Linear with a ready-for-agent triage label. - Use Case: After drafting a feature spec in conversation, ask for a ticket breakdown; the Skill proposes numbered tickets with blockers, quizzes you on granularity, then publishes the approved set in dependency order. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets with blocking edges and publish them to the configured tracker.