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 developers and agents cannot start work in the right order. ## Core Features & Use Cases - Vertical Slice Breakdown: Splits work into tracer-bullet tickets where each ticket cuts a complete path through schema, API, UI, and tests and is demoable on its own. - Blocking Edge Declaration: Every ticket declares which other tickets block it, so the workable frontier is always clear. - Flexible Publishing: Writes one local Markdown file per ticket under .scratch/<feature-slug>/issues/, or publishes native issues with blocking links to trackers like GitHub or Linear with a ready-for-agent label. - Wide Refactor Handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green. - Use Case: After drafting a feature spec, ask for a ticket breakdown; review the proposed numbered list with blocking edges, approve it, and have the tickets published to your tracker ready for agents to pick up. ## Quick Start Ask the assistant to break the current plan or a referenced spec into tracer-bullet tickets with blocking dependencies and publish them to the configured tracker.
