to-tickets SKILL.md skillA

to-tickets from kunolu/640-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add kunolu/640-skills/to-tickets@git:20261028.4eb8b2a

Pins git:20261028.4eb8b2a in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

kunolu/640-skills

Path

sbtd-workflow-onboard/assets/external-skills/stable/skills/to-tickets/SKILL.md

Versions recorded

4

Latest version

git:20261028.4eb8b2a, committed Oct 28, 2026

First version recorded

Jul 18, 2026

Size

5,812 bytes

Repository stars

557

License

Apache-2.0

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).

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# To Tickets

Break a plan, spec, or conversation into a set of **tickets**: tracer-bullet vertical slices, each declaring the tickets that **block** it.

The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`.

## Process

### 1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.

### 2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."

### 3. Draft vertical slices

Break the work into **tracer bullet** tickets.

<vertical-slice-rules>

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

Read the whole file at its exact version.

How to install

mdr add kunolu/640-skills/to-tickets@sha256:56ec23c5b2782785

[![mdr](https://markdownregistry.com/badge/art_q47o54r7moc5243m.svg)](https://markdownregistry.com/a/art_q47o54r7moc5243m)

Versions

The registry has recorded 4 versions of this file, between Jul 18, 2026 and Oct 28, 2026, about one every 34 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_q47o54r7moc5243m
GET https://markdownregistry.com/api/v1/resolve?ref=kunolu/640-skills/to-tickets
GET https://markdownregistry.com/api/v1/blob/56ec23c5b2782785d4e65bff9e315b6d3aeb4ef977c174a219e99489fada1995

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from kunolu/640-skills

Every file in kunolu/640-skills

Other files named to-tickets

Browse by kind, by grade A, or by owner.