plan-in-files skillA
plan-in-files is agent-read markdown (skill) from onewave-ai/claude-skills: Use for any task that spans more than a couple of steps, files, or sessions — refactors, migrations, multi-file features, anything that must survive a context reset or crash. Trigger when the user asks for a plan, says "keep track of this", "don't lose the thread", or when a task is large enough that forgetting step four is likely..
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
# Plan in Files A plan that lives in the conversation dies with the conversation. A plan that lives in a file survives a crash, a `/clear`, a laptop reboot, and a different person picking the work up on Monday. ## Core Behavior Before starting multi-step work, write the plan to disk. Update it as you go. The file is the source of truth about progress — not memory, not the chat. Default location: `PLAN.md` at the repo root for one-off work, or `docs/plans/<yyyy-mm-dd>-<topic>.md` when the repo keeps plan history. Gitignore it or commit it — ask once, then follow the repo's convention. ## Plan Shape ```markdown # <Task> — plan **Goal:** <one sentence, in the user's words> **Done when:** <the observable condition that ends this work> ## Constraints - <the things that must stay true: no API break, no new deps, ships today> ## Steps - [ ] 1. <action> — `path/to/file` - [ ] 2. <action> — `path/to/file` - [ ] 3. <action> — verify with `<command>` ## Notes <discoveries, gotchas, things that turned out to be false> ## Log - <date/time> — <what happened> ``` …
Read the whole file at its exact version.
How to install
mdr add onewave-ai/claude-skills/plan-in-files@git:20260920.97b5147mdr add onewave-ai/claude-skills/plan-in-files@sha256:2e2cb67218e28038Pin 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_ljtfyeg5z37fzfnl)
1 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 (3226 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
onewave-ai/claude-skills · 306 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ljtfyeg5z37fzfnl GET https://markdownregistry.com/api/v1/resolve?ref=onewave-ai/claude-skills/plan-in-files GET https://markdownregistry.com/api/v1/blob/2e2cb67218e280385d3d7c70bf93a30effa3cf36fd97404919f862774fd43e3f
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.