write-plan SKILL.md skillA
write-plan from teambrilliant/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add teambrilliant/dev-skills/write-plan@git:20261008.81e7416Pins git:20261008.81e7416 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- teambrilliant/dev-skills
- Path
skills/write-plan/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261008.81e7416, committed Oct 8, 2026
- First version recorded
- Sep 27, 2026
- Size
- 17,237 bytes
- Repository stars
- 5
- License
- none declared
Write a technical implementation plan to thoughts/plans/ before coding starts (separate from the harness's plan mode). Use when someone says "create a plan", "plan this", "plan this ticket", "how should we implement this", "technical design", "architect this", "plan the migration", "refactor plan", or when a shape or groomed ticket needs phases, layers, and agent-runnable checks.
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
# Write Plan Turn a shape, ticket, or technical challenge into a plan that any developer or agent can execute with `/dev-skills:execute-plan` — and that a human can read, understand, and defend. ## Workflow Every plan follows the same arc: **research → validate → write → present**. 1. **Research** the codebase until grounded — never plan from assumptions (see Process). 2. **Write** the plan to `thoughts/plans/YYYY-MM-DD-descriptive-name.md`, using today's date from context. 3. **Present** it for approval, closing with the ★ Plan View block. This skill is independent of any harness plan mode — always write the `thoughts/plans/` file. The gate is the user's approval of that file. Approval hands `execute-plan` a contract: it runs every phase to DONE or stops BLOCKED, without check-ins — so the plan must contain everything needed to get there unattended. ## Design Philosophy Before writing plans, read [references/software-design-philosophy.md](references/software-design-philosophy.md). Apply it to module boundaries, interfaces, and decomposition. Key checks: deep modules, information hiding, define errors out of existence, design it twice. ## Rollout & Rollback …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_e2rfkn2n7phzut7f/23c03576140a6a58672080b44f57f839865e90ac476dbd7d834a172a75ae2b2b.json
Then /plugin install write-plan@markdownregistry-e2rfkn2n7phzut7f in Claude Code. It installs git:20261008.81e7416, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add teambrilliant/dev-skills/write-plan@sha256:23c03576140a6a58The line at the top of this page pins the label git:20261008.81e7416, 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.
[](https://markdownregistry.com/a/art_e2rfkn2n7phzut7f)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in teambrilliant/dev-skills/write-plan since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of write-plan from somewhere else? Ask it: where did my write-plan come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Sep 27, 2026 and Oct 8, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.81e7416 latest | 2026-10-08 | 81e7416 | 17,237 B | A | view · diff |
| git:20261008.8e403b1 | 2026-10-08 | 8e403b1 | 17,588 B | A | view · diff |
| git:20260927.b9558d0 | 2026-09-27 | b9558d0 | 17,164 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/write-plan/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (17237 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
teambrilliant/dev-skills · 5 stars · license none declared · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e2rfkn2n7phzut7f GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/write-plan GET https://markdownregistry.com/api/v1/blob/23c03576140a6a58672080b44f57f839865e90ac476dbd7d834a172a75ae2b2b
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from teambrilliant/dev-skills
Every file in teambrilliant/dev-skills