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 any ordering. This Skill converts that context into vertical tracer-bullet tickets, each declaring exactly which other tickets block it, and publishes them to your 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. - Blocking edge management: Every ticket declares its blockers; wide refactors are sequenced as expand-migrate-contract batches so CI stays green. - Dual publishing targets: Writes one local file per ticket under .scratch/<feature-slug>/issues/ or publishes real issues with native blocking links and a ready-for-agent triage label on GitHub, Linear, or similar trackers. - 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 have the tickets published to your tracker in dependency order. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets and publish them to the configured tracker.
