to-tickets — Skills — getagentictools

What it does

Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer

A completed slice is demoable or verifiable on its own

Each slice is sized to fit in a single fresh context window

Any prefactoring should be done first

Title: short descriptive name

Blocked by: which other tickets (if any) must complete first

What it delivers: the end-to-end behaviour this ticket makes work

Source

Repository: https://github.com/mattpocock/skills

to-tickets FAQ

What does the to-tickets skill do?

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker. Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer A completed slice is demoable or verifiable on its own

What does to-tickets require?

Publish the approved tickets. How depends on the tracker /setup-matt-pocock-skills configured — the tickets are the same either way, only the shape of the blocking edges changes:

How do I install to-tickets?

Run: npx -y skills add https://github.com/mattpocock/skills --skill to-tickets --agent claude-code — the source lives at github.com/mattpocock/skills.

Maintain to-tickets?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![to-tickets on getagentictools](https://getagentictools.com/badge/skills/mattpocock-skills-to-tickets.svg)](https://getagentictools.com/skills/mattpocock-skills-to-tickets?ref=badge)

npx agentictools info skills/mattpocock-skills-to-tickets

The second line is the CLI lookup for this page — handy in READMEs and docs.