What problem does it solve? Turning a spec or plan into actionable work items is error-prone: tickets end up as horizontal layer slices that cannot be demoed, dependencies between tasks go undeclared, and issue bodies lack the context implementers need. This Skill decomposes any spec, plan, or conversation into vertical tracer-bullet tickets with explicit blocking edges and publishes them to the issue tracker. ## Core Features & Use Cases - Vertical slice decomposition: Drafts tracer-bullet tickets that cut through schema, API, UI, and tests so each one is independently demoable and fits a single context window. - Dependency modeling: Assigns blocking edges to every ticket, publishes issues in dependency order, and links them to the parent spec issue using the tracker contract in docs/agents/issue-tracker.md. - Quality-gated issue bodies: Enforces a five-point self-check on each ticket's Why statement before filing, and handles wide refactors via expand-contract sequencing instead of forced vertical slices. - Use Case: After finishing a feature spec, run this Skill to quiz you on a proposed ticket breakdown, then publish the approved tickets as tracker issues ready for implementation to work the unblocked frontier. ## Quick Start Ask the AI to break the current spec into tracer-bullet tickets with blocking dependencies and publish them to the issue tracker.
