to-tickets SKILL.md skillA

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

Install it, pinned

mdr add shaderera/shaderera/to-tickets@git:20261012.178eb1e

Pins git:20261012.178eb1e in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: shaderera/shaderera
Path: .claude/skills/to-tickets/SKILL.md
Versions recorded: 1
Latest version: git:20261012.178eb1e, committed Oct 12, 2026
Size: 5,839 bytes
Repository stars: 7
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

The exact contents, by fingerprint

mdr add shaderera/shaderera/to-tickets@sha256:38a3641add492b96

The line at the top of this page pins the label git:20261012.178eb1e, 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](https://markdownregistry.com/badge/art_hjv5rs6nic4lcj3e.svg)](https://markdownregistry.com/a/art_hjv5rs6nic4lcj3e)

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

Versions

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

version	committed	commit	size	audit
git:20261012.178eb1e latest	2026-10-12	178eb1e	5,839 B	A	view

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 (5839 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

shaderera/shaderera · 7 stars · license MIT · pushed 2026-10-31 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_hjv5rs6nic4lcj3e
GET https://markdownregistry.com/api/v1/resolve?ref=shaderera/shaderera/to-tickets
GET https://markdownregistry.com/api/v1/blob/38a3641add492b9641d520f36a716f5515e98e9e63883a5f0c20aa8ea19a2032

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 shaderera/shaderera

ask-matt SKILL.md skill

shaderera/shaderera · .claude/skills/ask-matt/SKILL.md · Ask which skill or flow fits your situation. A router over the skills in this repo.