implement-plan skillA
implement-plan is agent-read markdown (skill) from raffertyuy/repo-of-repos: Execute a plan from _plans/, implementing steps, checking off tasks, running tests, and documenting fixes.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Implement Plan Execute an implementation plan from `_plans/`, working through each step, updating the plan as you go, and running tests to verify. This skill combines the "implement" and "run" phases into one — you build it, run it, test it, fix it, and the plan documents everything that happened. ## Arguments The user provides the plan file to implement. For example: - `/implement-plan _plans/20260409-auth-ui.plan.md` - `/implement-plan auth-ui` (shorthand — resolve to the matching `.plan.md` file in `_plans/`) - `/implement-plan` (no argument — if only one plan has `status: draft` or `status: in-progress`, use that) ## Steps ### 1. Load the Plan 1. Read the plan file from `_plans/` 2. If the user gave a shorthand (no path or partial name), find the matching `.plan.md` file 3. If no argument and multiple draft/in-progress plans exist, ask the user which one 4. Parse the frontmatter and step list 5. Identify which steps are already checked (`- [x]`) and which are pending (`- [ ]`) ### 2. Read Per-Repo Instructions For each repo listed in the plan's `repos` frontmatter: 1. Check if `repos/<name>/CLAUDE.md` exists — if so, read and follow it …
Read the whole file at its exact version.
How to install
mdr add raffertyuy/repo-of-repos/implement-plan@git:20260723.1db5b32mdr add raffertyuy/repo-of-repos/implement-plan@sha256:c67780fbb891bbbdPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_k4fzu5zu7kofkadr)
2 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5050 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
raffertyuy/repo-of-repos · 12 stars · license MIT · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k4fzu5zu7kofkadr GET https://markdownregistry.com/api/v1/resolve?ref=raffertyuy/repo-of-repos/implement-plan GET https://markdownregistry.com/api/v1/blob/c67780fbb891bbbd65c8057d329710d48a171be549691b9e69c5236b9a6524e2
Your agent 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.
More from raffertyuy/repo-of-repos
Every file in raffertyuy/repo-of-repos