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 issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: 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 graph with blocking edges: Every ticket declares the tickets that must complete first, published as text references in local files or as native blocking links on GitHub, Linear, or similar trackers. - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract batches so CI stays green between steps. - Use Case: After drafting a feature spec, run this Skill to produce a numbered set of tickets under .scratch/<feature-slug>/issues/ or as real tracker issues labeled ready-for-agent, ready for agents to pick up in dependency order. ## Quick Start Ask the agent to break the current plan or spec into tracer-bullet tickets with blocking edges and publish them to the configured tracker.
