What problem does it solve? Turning a plan or spec into actionable work items is hard: tasks end up as horizontal layer slices that cannot be demoed, dependencies between tasks go undeclared, and tickets get published to trackers without any ordering. This Skill converts a plan, spec, or conversation into vertical tracer-bullet tickets, each declaring which tickets block it, and publishes them to a configured tracker. ## Core Features & Use Cases - Vertical slice breakdown: Splits work into tracer-bullet tickets that cut through every layer (schema, API, UI, tests) so each ticket is independently demoable and fits a single context window. - Dependency graph declaration: Every ticket declares its blocking edges, so agents and developers know exactly what can start immediately and what must wait. - Tracker publishing: Writes one file per ticket under .scratch/<feature-slug>/issues/ locally, or publishes 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 for a new billing flow, run this Skill to get a numbered set of tickets — prefactoring first, then vertical slices in dependency order — published to GitHub with blocking links so agents can pick up unblocked work immediately. ## 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 issue tracker.
