Verified:GitHub

to-tickets

Break plans and specs into tracer-bullet tickets with declared blocking edges.

Updated Jun 26, 2026

Search Tags:#project planning #issue tracker #github issues #dependency graph #vertical slice #tracer bullet #ticket breakdown

One-click install

npx skills add https://github.com/dulltackle/kangkang-skills --skill to-tickets-dulltackle

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/dulltackle/kangkang-skills/tree/main/to-tickets
Command: npx skills add https://github.com/dulltackle/kangkang-skills --skill to-tickets-dulltackle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tickets end up as horizontal layer slices that cannot be demoed, dependencies between tasks go undeclared, and teams lose track of what can start next. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking edges, and publishes them to your configured 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 declaration: Every ticket declares which tickets must complete first, so the workable frontier is always clear. - 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 issue tracker. ## Quick Start Ask the agent to break the current plan or a referenced spec into tracer-bullet tickets with blocking edges and publish them to the configured tracker.

Frequently Asked Questions about to-tickets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why does the Skill say the tracker is not configured?▼

The issue tracker and triage label vocabulary must be provided beforehand via the /setup-matt-pocock-skills setup step. If that configuration is missing, the Skill instructs you to run the setup before it can publish tickets.