Implement the result of /to-spec and /to-tickets in code.
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
You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.
The issue tracker should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`.
The goal is the entire spec implemented on a single **integration branch**, with every ticket resolved the way the issue tracker closes work.
The tickets are not a list of steps. They are a **task graph** with blocking relationships between them. This means there is always a **frontier** of tickets which are ready to be grabbed.
Communication to and from subagents should be sparse. Communicate primarily through **context pointers**: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.
**Implementer subagents** should be run in the background where possible for maximum concurrency.
## Steps
1. Read the spec and tickets to understand the task graph.
…
The line at the top of this page 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.
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 (2780 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 · 4 stars · license a license file GitHub does not identify · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_muaxd6n2ah7znsmd
GET https://markdownregistry.com/api/v1/resolve?ref=miklschmidt/archboard/implement-spec
GET https://markdownregistry.com/api/v1/blob/7a22dd2e60b8fcece478ced9d2533582adf3520d695acd3ab715341535c9e56d
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.
miklschmidt/archboard · .agents/skills/claude-handoff/SKILL.md · Hand the current conversation off to a fresh background agent that picks up the work immediately.
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…
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…
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…
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…
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.
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…
miklschmidt/archboard · .agents/skills/impeccable/SKILL.md · Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt…
dzhng/skills · skills/engineering/implement-spec/SKILL.md · Implement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints…
jellydn/my-ai-tools · skills/implement-spec/SKILL.md · Implement a complete spec from its ticket graph, using isolated workers and one integration branch.
jellydn/my-ai-tools · configs/amp/plugins/my-ai-tools-skills/skills/implement-spec/SKILL.md · Implement a complete spec from its ticket graph, using isolated workers and one integration branch.
dzhng/duet-agent · .agents/skills/implement-spec/SKILL.md · Implement an existing spec through committed passes. Use for long or multi-pass specs that need maintenance checkpoints…
