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 ship independently, and dependencies between tasks go untracked. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which other tickets block it, and publishes them to your configured issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: Splits work into narrow but complete slices cutting through schema, API, UI, and tests, each demoable on its own and sized for a single context window. - Dependency graph declaration: Every ticket declares its blocking edges, so agents and developers always know which tickets are ready to work (the frontier). - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green batch to batch. - Flexible publishing: Writes one Markdown file per ticket under .scratch/<feature-slug>/issues/ locally, or creates native issues with blocking links and a ready-for-agent label on trackers like GitHub or Linear. - Use Case: After drafting a feature spec in conversation, ask the agent to break it into tickets; it proposes a numbered breakdown with blocking edges, iterates with you on granularity, then publishes the approved tickets to your tracker. ## 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 tracker.
