What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up as horizontal layer-by-layer slices that cannot be demoed, dependencies between tasks go undeclared, and tickets get published to a tracker without any structure an agent or teammate can pick up. ## Core Features & Use Cases - Vertical slice breakdown: Splits work into tracer-bullet tickets that each cut a complete path through schema, API, UI, and tests, sized to fit a single context window. - Blocking edge declaration: Every ticket declares which other tickets block it, published as text edges in local files or as native blocking links on GitHub, Linear, or another configured tracker. - Wide refactor handling: Sequences large mechanical refactors as expand-migrate-contract ticket chains so CI stays green batch to batch. - Use Case: After drafting a feature spec, ask for a ticket breakdown; review the proposed numbered list with blocking edges, iterate on granularity, then publish one issue per ticket to your tracker with a ready-for-agent label. ## Quick Start Break the attached feature spec into tracer-bullet tickets with blocking edges and publish them to my issue tracker.
