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 decomposition: Each ticket cuts a complete path through schema, API, UI, and tests, sized to fit a single fresh context window and demoable on its own. - Blocking edge modeling: Every ticket declares its blockers; wide refactors are sequenced as expand-migrate-contract batches measured by blast radius instead of forced into tracer bullets. - Dual publishing targets: Writes one Markdown file per ticket under .scratch/<feature-slug>/issues/ locally, or creates native issues with 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 titles, blocking edges, and deliverables, approve the granularity, then publish the ordered tickets to your repo's GitHub issues. ## Quick Start Break the current plan in this conversation into tracer-bullet tickets with blocking edges and publish them to this repo's issue tracker.
