implementation-plan skillA
implementation-plan is agent-read markdown (skill) from fmind/dot: Turn accepted requirements into repository-grounded implementation steps and verification, or challenge a plan through assumptions, failure modes, and trade-offs..
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 against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Implementation Plan Design the smallest sequence of independently verifiable vertical slices that satisfies accepted requirements, or challenge an existing plan before it is executed; implementation follows the accepted scope and applicable stack skills. ## Workflow To write a plan, follow the steps below. To challenge an existing plan, read only [plan-review](references/plan-review.md); to settle an unfamiliar API or architecture choice first, read [research-brief](references/research-brief.md). 1. **Read the accepted scope**: identify the outcome, constraints, authorization, and unresolved decisions; stop planning when material options still need a user decision. 1. **Inspect the implementation**: verify relevant paths, interfaces, dependencies, tests, and current work; preserve user changes and reuse existing mechanisms. 1. **Choose useful slices**: order the smallest independently verifiable changes by dependency; identify shared files and real compatibility or migration risks. 1. **Specify proof**: each slice names its outcome, affected files, dependencies, implementation steps, focused checks with expected results, and objective acceptance criteria. …
Read the whole file at its exact version.
How to install
mdr add fmind/dot/implementation-plan@git:20260919.4491844mdr add fmind/dot/implementation-plan@sha256:e2dfc3f88fdfd950Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_bbklw36cnqlfo7iy)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.4491844 latest | 2026-09-19 | 4491844 | 3,766 B | A | view · diff |
| git:20260916.50d6810 | 2026-09-16 | 50d6810 | 3,211 B | A | view · diff |
| git:20260908.131d2e1 | 2026-09-08 | 131d2e1 | 3,284 B | A | view · diff |
| git:20260906.ede7325 | 2026-09-06 | ede7325 | 3,332 B | A | view · diff |
| git:20260906.a4e0ec8 | 2026-09-06 | a4e0ec8 | 3,425 B | A | view |
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 (3766 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
fmind/dot · 9 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bbklw36cnqlfo7iy GET https://markdownregistry.com/api/v1/resolve?ref=fmind/dot/implementation-plan GET https://markdownregistry.com/api/v1/blob/e2dfc3f88fdfd9509a4609db7ddeae11ce28c109124137fcd1d628c84f723dd7
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.