to-tickets SKILL.md skillA

The newest version of a file that held these bytes earlier

to-tickets in mattpocock/skills is at git:20261006.9e2abf8 (Oct 6, 2026), graded A.

mdr add mattpocock/skills/to-tickets@git:20261006.9e2abf8

This copy is 2 versions behind it. See what changed · install this older copy instead

This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.

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

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
miklschmidt/archboard
Path
.agents/skills/to-tickets/SKILL.md
Versions recorded
1
Latest version
git:20261025.3b43540, committed Oct 25, 2026
Size
5,671 bytes
Repository stars
11
License
a license file GitHub does not identify

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

This older copy, pinned
mdr add miklschmidt/archboard/to-tickets@git:20261025.3b43540

Pins git:20261025.3b43540 in mdr.lock, 2 versions behind the newest at the top of this page.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ito3womoxdzky6m5/5c9fba69845c2519b9b35b9af42ae5142c21f8ca15ac2123dc2722002c8058ae.json

Then /plugin install to-tickets@markdownregistry-ito3womoxdzky6m5 in Claude Code. It installs git:20261025.3b43540, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add miklschmidt/archboard/to-tickets@sha256:5c9fba69845c2519

The older copy line above pins the label git:20261025.3b43540, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

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

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: get me the newest mattpocock/skills/to-tickets, and what changed since 5c9fba6? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of to-tickets from somewhere else? Ask it: where did my to-tickets come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Oct 25, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261025.3b43540 latest2026-10-25 3b43540 5,671 BA view

Copies

The newest version, then this copy

Newest: git:20261006.9e2abf8 of to-tickets in mattpocock/skills (skills/engineering/to-tickets/SKILL.md), graded A.

This copy: byte for byte that file's version git:20260819.3216582, which it committed on Aug 19, 2026, before this repository did; graded A, 2 versions behind.

See what changed since these bytes · ask your agent

Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.

Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5671 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

miklschmidt/archboard · 11 stars · license a license file GitHub does not identify · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ito3womoxdzky6m5
GET https://markdownregistry.com/api/v1/resolve?ref=miklschmidt/archboard/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 miklschmidt/archboard

ask-matt SKILL.md skill
miklschmidt/archboard · .agents/skills/ask-matt/SKILL.md · Ask which skill or flow fits your situation. A router over the skills in this repo.
git:20261025.3b43540 · audit A · 11 stars
claude-handoff SKILL.md skill
miklschmidt/archboard · .agents/skills/claude-handoff/SKILL.md · Hand the current conversation off to a fresh background agent that picks up the work immediately.
git:20261025.3b43540 · audit A · 11 stars
code-review SKILL.md skill
miklschmidt/archboard · .agents/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
git:20261025.3b43540 · audit A · 11 stars
codebase-design SKILL.md skill
miklschmidt/archboard · .agents/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
git:20261025.3b43540 · audit A · 11 stars
diagnosing-bugs SKILL.md skill
miklschmidt/archboard · .agents/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
git:20261025.3b43540 · audit A · 11 stars
domain-modeling SKILL.md skill
miklschmidt/archboard · .agents/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
git:20261025.3b43540 · audit A · 11 stars
grill-me SKILL.md skill
miklschmidt/archboard · .agents/skills/grill-me/SKILL.md · A relentless interview to sharpen a plan or design.
git:20261025.3b43540 · audit B · 11 stars
grill-with-docs SKILL.md skill
miklschmidt/archboard · .agents/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
git:20261025.3b43540 · audit A · 11 stars
grilling SKILL.md skill
miklschmidt/archboard · .agents/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
git:20261025.3b43540 · audit A · 11 stars
handoff SKILL.md skill
miklschmidt/archboard · .agents/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
git:20261025.3b43540 · audit A · 11 stars
impeccable SKILL.md skill
miklschmidt/archboard · .agents/skills/impeccable/SKILL.md · Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt…
v4.3.1 · audit A · 11 stars
implement-spec SKILL.md skill
miklschmidt/archboard · .agents/skills/implement-spec/SKILL.md · Implement the result of /to-spec and /to-tickets in code.
git:20261025.3b43540 · audit A · 11 stars

Every file in miklschmidt/archboard

Other files named to-tickets

to-tickets SKILL.md skill
mattpocock/skills · skills/engineering/to-tickets/SKILL.md · Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges…
git:20261006.9e2abf8 · audit A · 327,521 stars
to-tickets SKILL.md skill
vinvcn/mattpocock-skills-zh-cn · skills/engineering/to-tickets/SKILL.md · 把 plan、spec 或当前对话拆成一组 tracer-bullet tickets,每个 ticket 声明 blocking edges,并发布到已配置的 tracker;本地用每 ticket 一个文件中的文本 edge,真实…
git:20261028.c48fd4a · audit A · 5,886 stars
to-tickets SKILL.md skill
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/skills/to-tickets/SKILL.md · Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges…
git:20261028.4eb8b2a · audit A · 559 stars
to-tickets SKILL.md skill
asymmetric-al/core · .agents/skills/to-tickets/SKILL.md · Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges…
git:20261023.f970aa0 · audit A · 370 stars
to-tickets SKILL.md skill
timharris707/skills · skills/run/to-tickets/SKILL.md · Turn a plan, a spec, a closed decision map, or a pressure-tested conversation into tracer-bullet work items on the…
git:20261008.0b04f1c · audit A · 46 stars
to-tickets SKILL.md skill
timharris707/skills · plugins/clickai-codex/skills/run/to-tickets/SKILL.md · When asked to file tickets, break down approved work, or move a settled plan onto the board, turn the spec, closed…
git:20261008.0b04f1c · audit A · 46 stars
to-tickets SKILL.md skill
hitesit/real-scientist-skills · skills/engineering/to-tickets/SKILL.md · Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges…
git:20261006.9e2abf8 · audit A · 38 stars
to-tickets SKILL.md skill
svyatov/supermatt · skills/to-tickets/SKILL.md · Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges…
git:20261018.f19c25a · audit A · 30 stars

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

Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.