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 your configured tracker. ## Core Features & Use Cases - Vertical slice decomposition: Splits work into narrow end-to-end slices spanning schema, API, UI, and tests, each demoable on its own and sized for a single context window. - Blocking edge modeling: Every ticket declares its blockers, so the team can work the frontier — any ticket whose blockers are done. - Wide refactor handling: Sequences large mechanical changes as expand–migrate–contract ticket chains that keep CI green batch to batch. - Flexible publishing: Writes one local file per ticket under .scratch/<feature-slug>/issues/, or creates real issues with native blocking links and a ready-for-agent label on GitHub, Linear, or similar trackers. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it proposes a numbered breakdown with blocking edges, iterates with you on granularity, then publishes the approved set to your tracker. ## Quick Start Ask the agent to break the current plan or spec into tracer-bullet tickets with blocking dependencies and publish them to the configured tracker.
