What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up too coarse, dependencies stay implicit, and tickets get written as horizontal layer-by-layer slices that cannot be demoed. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to a local file structure or a real issue tracker. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits work into narrow but complete slices cutting through schema, API, UI, and tests, each sized to fit a single context window. - Dependency Modeling: Assigns every ticket its blocking edges so the team always knows which frontier tickets can start immediately. - Wide Refactor Handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green batch to batch. - Tracker Publishing: Writes one file per ticket under .scratch/<feature-slug>/issues/ locally, or creates native blocking issues on GitHub or Linear with a ready-for-agent triage label. - Use Case: After drafting a feature spec for a new billing flow, run this Skill to produce six ordered tickets with acceptance criteria and blocking links, ready for agents or engineers to pick up. ## 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.
