skills.rest
IsKenKenYa
IsKenKenYaCOMMUNITY
Explore all skills by this author →
GitHub

to-tickets

Breaks plans and specs into tracer-bullet tickets with declared blocking dependencies.

2|Updated Jun 21, 2026
Search Tags:#issue tracker#task breakdown#github issues#vertical slice#tracer bullet#dependency planning#ticket decomposition
One-click install
npx skills add https://github.com/IsKenKenYa/skills --skill to-tickets-iskenkenya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/IsKenKenYa/skills/tree/main/skills/engineering/to-tickets
Command: npx skills add https://github.com/IsKenKenYa/skills --skill to-tickets-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is hard: tasks end up as horizontal layer-by-layer slices that cannot be demoed, dependencies between tasks go undeclared, and tickets live in inconsistent formats. This Skill decomposes work into vertical tracer-bullet tickets, each with explicit blocking relationships, and publishes them to a configured issue tracker or local files. ## 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/ in local mode, or creates real issues with native blocking links and a ready-for-agent label on trackers like GitHub or Linear. - Use Case: After drafting a feature spec for a new checkout flow, run this Skill to produce six ordered tickets where the UI ticket is blocked by the API ticket, publish them to GitHub, and hand them off to coding agents. ## 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.

Frequently Asked Questions about to-tickets

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

FAQPage Schema
How do I break a feature spec into tickets for coding agents?▼

Provide the spec path, issue number, or URL as an argument and the Skill drafts vertical tracer-bullet slices, each with blocking edges and acceptance criteria. After you approve the breakdown, it publishes one ticket per slice to your configured tracker in dependency order.

What is a tracer-bullet ticket in task decomposition?▼

A tracer-bullet ticket is a narrow but complete vertical slice cutting through every layer (schema, API, UI, tests) rather than a horizontal slice of one layer. Each finished slice is demoable or verifiable on its own and sized to fit a single fresh context window.

Can I publish tickets to GitHub or Linear instead of local files?▼

Yes. The tracker is configured by the setup-matt-pocock-skills Skill. Real trackers get one issue per ticket with native blocking or sub-issue links and a ready-for-agent label; local mode writes numbered Markdown files under .scratch/<feature-slug>/issues/.

How are large refactors handled when vertical slicing is impossible?▼

Wide refactors use expand-contract sequencing: add the new form beside the old, migrate call sites in blast-radius-sized batches as separate blocked tickets, then delete the old form last. If batches cannot stay green alone, they share an integration branch gating a final verify ticket.

Why does the Skill say the issue tracker was not provided?▼

The tracker configuration and triage label vocabulary come from the setup-matt-pocock-skills Skill. If they are missing, run /setup-matt-pocock-skills first so to-tickets knows where and how to publish tickets.

Related Skills

Explore More Software Engineering Skills→
dnkrowdnkrow
1

reverse-document

Generate design or architecture documentation from existing code or prototypes.

Community
Intermediate
mambo-wangmambo-wang
3

to-tickets

Breaks plans and specs into tracer-bullet tickets with declared blocking dependencies.

Community
Intermediate
sek788432sek788432
6

code-review

Reviews a change set against coding standards and its originating spec on two independent axes.

Community
Intermediate
jacksonlee-twjacksonlee-tw

planning-and-task-breakdown

Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.

Community
Intermediate