skills.rest
yamcodes
yamcodesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-tickets

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

1|Updated Aug 24, 2026
Search Tags:#planning#github#issue tracker#task breakdown#tickets#dependency graph#vertical slice
One-click install
npx skills add https://github.com/yamcodes/the-hat --skill to-tickets-yamcodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-tickets
Source: https://github.com/yamcodes/the-hat/tree/main/skills/to-tickets
Command: npx skills add https://github.com/yamcodes/the-hat --skill to-tickets-yamcodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or long conversation into actionable work items is error-prone: slices end up horizontal, dependencies stay implicit, and tickets lose traceability. This Skill converts that context into vertical tracer-bullet tickets, each declaring exactly which other tickets block it, and publishes them to your configured tracker. ## Core Features & Use Cases - Vertical Slice Breakdown: 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 lists the tickets that gate it, published as text references in local files or as native blocking links on GitHub, Linear, or similar trackers. - Wide Refactor Sequencing: Handles codebase-wide mechanical changes via expand-contract migration batches instead of forcing them into tracer bullets. - Use Case: After drafting a feature spec in chat, ask the assistant to break it into tickets; it proposes a numbered breakdown, quizzes you on granularity and dependencies, then publishes one issue per ticket in dependency order with a ready-for-agent label. ## 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.

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?▼

Provide the spec path, issue URL, or work from the current conversation, and the Skill drafts vertical tracer-bullet slices. Each ticket declares its blocking edges, and you review granularity and dependencies before anything is published.

What is a tracer-bullet vertical slice ticket?▼

A tracer-bullet ticket cuts a narrow but complete path through every layer, including schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own and sized to fit a single context window.

Can I publish tickets to GitHub or Linear?▼

Yes, the Skill publishes one issue per ticket in dependency order using the tracker's native blocking or sub-issue relationships where available. Without a real tracker, it writes one markdown file per ticket under .scratch with blocking edges listed as text.

How are wide refactors handled in ticket breakdowns?▼

Wide refactors are sequenced as expand-contract instead of vertical slices: add the new form beside the old, migrate call sites in blast-radius-sized batches, then delete the old form. Each batch is its own ticket with appropriate blocking edges.

Why does the Skill ask me to run setup-matt-pocock-skills?▼

The Skill needs a configured issue tracker and triage label vocabulary before publishing tickets. If that configuration is missing, it instructs you to run /setup-matt-pocock-skills to provide it.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

architecture-decision

Document Architecture Decision Records with context, alternatives, and consequences.

Community
Advanced
MaxWolf-01MaxWolf-01
3

to-tickets

Breaks a grilled specification into dependency-ordered tracer-bullet ticket files with blocking edges.

Community
Advanced
narrative-ionarrative-io

shortcut-ticket

Create Shortcut tickets with problem statements, acceptance criteria, SOC-2 notes, and implementation plans.

Official
Advanced
tDaliletDalile

gsd:add-todo

Add todo items with titles and metadata to a tracking list.

Community
Basic