Skip to content
SkillModel-led1,201 tokens in use

to-tickets

Break a plan or spec into tracer-bullet tickets with declared blocking edges and publish them to your tracker.

328,764 stars on the repository MIT Licensemattpocock/skills · skills/engineering/to-tickets
claude plugin install mattpocock-skills@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing to-tickets costs

54tokens idle
1,201tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts and code blocks. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Fair
  • Frontmatter8/15
  • Structure17/25
  • Examples3/15
  • Output10/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community56
  • Maturity32
  • Momentum40

to-tickets splits a plan, spec or conversation into vertical-slice tickets. Each slice cuts a narrow but complete path through every layer, can be verified on its own, and fits in one fresh context window. Each ticket names the tickets that block it.

The breakdown is presented as a numbered list for you to approve before anything is published.

What You Get

  • A set of tickets that each deliver demoable end-to-end behaviour
  • Blocking edges so you can see which tickets can start immediately
  • Acceptance criteria as a checklist per ticket
  • Expand-contract sequencing for wide refactors

Common Use Cases

  • Turn a spec into work an agent can pick up ticket by ticket
  • Plan a column rename or shared type change as expand, migrate and contract tickets
  • Create local ticket files for a solo project with no remote tracker

What Makes It Unique

It treats blocking edges as first-class and publishes in dependency order so edges can reference real identifiers. Wide refactors get expand-contract batches, which keep CI green where a single vertical slice could not land. It also looks for prefactoring opportunities and quizzes you on granularity before publishing.

Under The Hood

A single SKILL.md with two embedded templates, one for local ticket files and one for tracker issues. It fetches an issue or spec you point to, explores the codebase, and publishes through whichever tracker setup-matt-pocock-skills configured. It marks tickets ready-for-agent and leaves any parent issue unchanged.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers