Decompose a spec, plan, or discussion into tracer-bullet tickets with explicit dependency edges. Use when the user invokes /to-tickets or asks to break down a plan into actionable tickets.
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 & verify Goldfish Gate
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.
**Goldfish Gate Check**: Ensure the originating specification has passed a zero-context Goldfish review (`/egm-review`). Never decompose an unverified spec or casual conversation draft into tickets: unstated assumptions in the spec multiply across tickets and degrade parallel agent execution. If the spec has not undergone Goldfish review, run `/egm-review` first.
### 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.
…
The line at the top of this page pins the label git:20261028.2d7a246, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_bhdh77dempki3jq4
GET https://markdownregistry.com/api/v1/resolve?ref=saifallah-star/aegis/to-tickets
GET https://markdownregistry.com/api/v1/blob/4ad69e29c9a5d8e039e0369587fe22aedd961742c0eaf9a8f0cf4493f98dcacc
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.
saifallah-star/aegis · .agents/skills/ask-matt/SKILL.md · Router to help choose the right skill or engineering workflow for your situation. Use when the user asks for guidance…
saifallah-star/aegis · .agents/skills/codebase-design/SKILL.md · Shared vocabulary and principles for designing deep modules with narrow interfaces. Use when designing module…
saifallah-star/aegis · .agents/skills/diagnosing-bugs/SKILL.md · Disciplined diagnosis loop for hard bugs and performance regressions: reproducible test -> isolate -> hypothesis ->…
saifallah-star/aegis · .agents/skills/domain-modeling/SKILL.md · Actively build and sharpen a project's ubiquitous domain language, glossary, and Architectural Decision Records (ADRs)…
saifallah-star/aegis · .agents/skills/grill-me/SKILL.md · Interview the user relentlessly about a plan, idea, or decision until all branches of the design tree are settled. Use…
saifallah-star/aegis · .agents/skills/grill-with-docs/SKILL.md · Relentless interview session to stress-test and clarify a design or plan while creating GLOSSARY.md and ADRs inline…
saifallah-star/aegis · .agents/skills/grilling/SKILL.md · Core interviewing primitive that maps decisions into a branching design tree, working the frontier one round of…
saifallah-star/aegis · .agents/skills/handoff/SKILL.md · Serialize the active conversation context into a structured handoff document for another agent or future session to…
saifallah-star/aegis · .agents/skills/implement-spec/SKILL.md · Execute an entire spec on an integration branch by coordinating implementer subagents across a ticket task graph…
saifallah-star/aegis · .agents/skills/implement/SKILL.md · Build out work based on a spec or tickets by driving TDD at pre-agreed seams and closing with code review. Use when the…
saifallah-star/aegis · .agents/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for module deepening and refactoring opportunities, generate an interactive HTML report, and grill…
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…
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…
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…
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…
vodailocz/kilo-kit-mcp · 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…
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…
mambo-wang/codewiki-plus · .codebuddy/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…