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 goal is a PR which implements the entire spec on a single branch.
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. Read enough to understand the task graph.
2. (optional) Use an **exploration subagent** to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets **implementer subagents** focus on implementation rather than exploration.
…
The line at the top of this page pins the label git:20260916.5a385b8, 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_cfdi7op25mrdkfiz
GET https://markdownregistry.com/api/v1/resolve?ref=mambo-wang/codewiki-plus/implement-spec
GET https://markdownregistry.com/api/v1/blob/f703b5f41df9c2202e19540d203e0d5fc32613572a838a070136cc22e712b129
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.
mambo-wang/codewiki-plus · .codebuddy/skills/blog-writing-specialist/SKILL.md · Comprehensive blog writing skill that handles technical blog posts, personal voice writing, brain dump transformation…
mambo-wang/codewiki-plus · .codebuddy/skills/claude-handoff/SKILL.md · Hand the current conversation off to a fresh background agent that picks up the work immediately.
mambo-wang/codewiki-plus · .codebuddy/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…
mambo-wang/codewiki-plus · .codebuddy/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…
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…
