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 be demoed, dependencies between tasks go undeclared, and tickets get published inconsistently across trackers. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to a local file store 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 demoable on its own and sized for a single context window. - Blocking edge modeling: Every ticket declares which other tickets gate it, so agents and developers always know the workable frontier. - Wide refactor handling: Sequences large mechanical changes as expand-migrate-contract ticket chains that keep CI green batch to batch. - Dual publishing targets: 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 GitHub, Linear, or similar trackers. - Use Case: After drafting a feature spec for a new billing flow, run this Skill to get a numbered, dependency-ordered set of tickets you can approve interactively and publish straight to your tracker. ## Quick Start Ask the assistant to break the current plan or a referenced spec into tracer-bullet tickets with blocking edges and publish them to the configured tracker.
