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 can't ship independently, dependencies between tasks go undeclared, and tickets get published to trackers without any structure an agent or teammate can pick up. ## Core Features & Use Cases - Vertical slice breakdown: Splits work into tracer-bullet tickets where each slice cuts through every layer (schema, API, UI, tests) and is demoable on its own. - Blocking edge declaration: Every ticket declares which other tickets block it, published as text in local per-ticket files or as native blocking links on GitHub, Linear, or other trackers. - 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 the agent to break it into tickets; it proposes a numbered breakdown with blocking edges, quizzes you on granularity, then publishes approved tickets to your configured tracker with a ready-for-agent label. ## 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.
