What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is error-prone: tickets end up as horizontal layer slices, dependencies stay implicit, and nothing is sized for a single focused implementation session. This Skill decomposes work 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 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. - Explicit blocking edges: Every ticket declares its blockers, published as text in local per-ticket files or as native blocking links on GitHub, Linear, or similar trackers. - Wide-refactor handling: Large mechanical changes are sequenced as expand-migrate-contract batches instead of being forced into a single slice. - 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 one issue per ticket in dependency order with a ready-for-agent label. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets and publish them to the configured issue tracker.
