What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up too coarse, horizontally sliced by layer, or missing dependency information, so agents and developers cannot pick up work independently. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to a local file structure or a real issue 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 a single context window. - Blocking edge modeling: Every ticket declares which other tickets gate it, published as text references in local files or native blocking links on GitHub, Linear, and similar trackers. - Wide refactor handling: Large mechanical changes are sequenced as expand-migrate-contract ticket chains instead of being forced into a single slice. - Use Case: After drafting a feature spec for a new commenting system, ask the agent to break it into tickets; it proposes a numbered breakdown with dependencies, quizzes you on granularity, then publishes one issue per ticket 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 tracker.
