What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is error-prone: slices end up horizontal, dependencies stay implicit, and tickets land in the tracker without clear ordering. This Skill decomposes work into vertical tracer-bullet tickets, each declaring which other tickets block it, and publishes them to the configured issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: Splits work into narrow end-to-end slices spanning schema, API, UI, and tests, each demoable on its own and sized for a single context window. - Blocking edge modeling: Every ticket declares its blockers, and wide refactors are sequenced as expand-migrate-contract batches that keep CI green. - Tracker publishing: Writes one file per ticket under .scratch/<feature-slug>/issues/ locally, or creates native blocking issues on GitHub, Linear, or similar trackers with the ready-for-agent label. - Use Case: After drafting a feature spec, ask the agent to break it into tickets; it proposes a numbered breakdown with dependencies, quizzes you on granularity, then publishes the approved set to your tracker in dependency order. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets with blocking dependencies and publish them to the configured tracker.
