to-tickets SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.

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

mdr add chinkan/rustfox/to-tickets@git:20260922.53f91f6

Pins git:20260922.53f91f6 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

chinkan/rustfox

Path

.agents/skills/to-tickets/SKILL.md

Versions recorded

2

Latest version

git:20260922.53f91f6, committed Sep 22, 2026

First version recorded

Jul 14, 2026

Size

5,671 bytes

Repository stars

11

License

MIT

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 chinkan/rustfox/to-tickets@sha256:5c9fba69845c2519

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

Versions

The registry has recorded 2 versions of this file, between Jul 14, 2026 and Sep 22, 2026, about one every 71 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_6mrnncuteoy5leep
GET https://markdownregistry.com/api/v1/resolve?ref=chinkan/rustfox/to-tickets
GET https://markdownregistry.com/api/v1/blob/5c9fba69845c2519b9b35b9af42ae5142c21f8ca15ac2123dc2722002c8058ae

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 chinkan/rustfox

Every file in chinkan/rustfox

Other files named to-tickets

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