What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up as horizontal layer-slices that cannot be demoed, dependencies between tasks stay implicit, and tickets get published to a tracker without any blocking structure. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which other tickets block it, and publishes them to a configured tracker. ## Core Features & Use Cases - Vertical slice decomposition: Splits work into narrow but complete slices cutting through schema, API, UI, and tests, each sized to fit a single fresh context window. - Blocking edge modeling: Every ticket declares the tickets that must complete first, published as text edges 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 ticket chains so CI stays green batch to batch. - 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 tracker.
