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. ## 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 fresh context window. - Blocking Edge Declaration: Every ticket declares which other tickets block it, published as text edges in local per-ticket files or as native blocking links on GitHub, Linear, or similar trackers. - Expand-Contract Sequencing: Handles wide refactors (renames, retypes with large blast radius) as expand, batched migrate, and contract ticket sequences instead of forcing them into vertical slices. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it quizzes you on granularity and dependencies, 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 issue tracker.