write-plan SKILL.md skillA

write-plan from fredwu/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add fredwu/dotfiles/write-plan@git:20261107.665a973

Pins git:20261107.665a973 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
fredwu/dotfiles
Path
ai/skillshare/skills/write-plan/SKILL.md
Versions recorded
5
Latest version
git:20261107.665a973, committed Nov 7, 2026
First version recorded
Oct 25, 2026
Size
6,021 bytes
Repository stars
18
License
none declared

Investigate a repository or workflow read-only and save an evidence-backed architectural plan with outcome-based phases and acceptance criteria.

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

Investigate read-only and save a self-contained plan that defines the architecture, intended outcomes, and acceptance criteria. Leave routine implementation decisions to execution. Create or edit only that plan; do not change implementation or external state, and do not execute the plan.

Read and apply [Plan standards](references/plan-standards.md) and [Resolve plan requirements](references/requirements.md).

## Original planning

Before you investigate, exclude all other plans in the repository. Do not discover, read, search, compare, or reuse them, and do not derive requirements, decisions, structure, sequencing, or findings from them. Exclude plan files and directories from broad content searches. You can check whether a destination path exists, without reading existing plans.

The exclusion also covers delegated research and review, and plan content in summaries, memory, or already-loaded context. Ground the plan in current user requirements, repository instructions, the actual implementation and tests, and non-plan documentation. When the requirements reference falls back to stored requirements or digests, it must not use other plans or plan-derived material.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_k4b6qt5qxvhidl3t/62e6aadbe4eb7cfaa050d042935c4dfdcd443f5d1cccf269d605e17255ac82cc.json

Then /plugin install write-plan@markdownregistry-k4b6qt5qxvhidl3t in Claude Code. It installs git:20261107.665a973, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add fredwu/dotfiles/write-plan@sha256:62e6aadbe4eb7cfa

The line at the top of this page pins the label git:20261107.665a973, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_k4b6qt5qxvhidl3t.svg)](https://markdownregistry.com/a/art_k4b6qt5qxvhidl3t)

3 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in fredwu/dotfiles/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 5 versions of this file, between Oct 25, 2026 and Nov 7, 2026, about one every 3 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261107.665a973 latest2026-11-07 665a973 6,021 BA view · diff
git:20261107.aae99872026-11-07 aae9987 10,392 BA view · diff
git:20261030.484f1352026-10-30 484f135 9,829 BA view · diff
git:20261025.83f68e32026-10-25 83f68e3 9,698 BA view · diff
git:20261025.112a2af2026-10-25 112a2af 9,068 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6021 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

GitHub

fredwu/dotfiles · 18 stars · license none declared · pushed 2026-11-17 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_k4b6qt5qxvhidl3t
GET https://markdownregistry.com/api/v1/resolve?ref=fredwu/dotfiles/write-plan
GET https://markdownregistry.com/api/v1/blob/62e6aadbe4eb7cfaa050d042935c4dfdcd443f5d1cccf269d605e17255ac82cc

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 fredwu/dotfiles

AGENTS.md AGENTS.md file
fredwu/dotfiles · AGENTS.md
git:20261107.665a973 · audit A · 18 stars
CLAUDE.md CLAUDE.md file
fredwu/dotfiles · CLAUDE.md
git:20261107.665a973 · audit B · 18 stars
AGENTS.md@ai/shared AGENTS.md file
fredwu/dotfiles · ai/shared/AGENTS.md
git:20261112.5a8332d · audit A · 18 stars
agent-device SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/agent-device/SKILL.md · Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices…
git:20260927.525f082 · audit A · 18 stars
ask-me SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/ask-me/SKILL.md · Find the open decisions in the current context that need the user, ask only the ambiguous, critical, or hard-to-reverse…
git:20261111.6b07b08 · audit A · 18 stars
claude-review-loop SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/claude-review-loop/SKILL.md · Review and remediate code through bounded Claude rounds, preferring T3's orchestrator with ACP fallback. Use only when…
git:20261107.665a973 · audit A · 18 stars
claude-review SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/claude-review/SKILL.md · Run one read-only Claude review through T3's orchestrator when available, with ACP fallback. Use only when explicitly…
git:20261107.665a973 · audit A · 18 stars
code-review-loop SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/code-review-loop/SKILL.md · Review, remediate, and verify code through bounded rounds. Use for review-and-fix requests; use code-review for one…
git:20261107.665a973 · audit A · 18 stars
code-review SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/code-review/SKILL.md · Review a code target once without edits for concrete, in-scope defects. Use code-review-loop for review and remediation.
git:20261107.665a973 · audit A · 18 stars
codex-review-loop SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/codex-review-loop/SKILL.md · Review and remediate code through bounded Codex rounds, preferring T3's orchestrator with ACP fallback. Use only when…
git:20261107.665a973 · audit A · 18 stars
codex-review SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/codex-review/SKILL.md · Run one read-only Codex review through T3's orchestrator when available, with ACP fallback. Use only when explicitly…
git:20261107.665a973 · audit A · 18 stars
compare-plans SKILL.md skill
fredwu/dotfiles · ai/skillshare/skills/compare-plans/SKILL.md · Compare the current completed analysis plan with one or more supplied or identifiable peer plans and return prioritized…
git:20261107.665a973 · audit A · 18 stars

Every file in fredwu/dotfiles

Other files named write-plan

write-plan SKILL.md skill
ovich/swarmstorm · skills/plan/write-plan/SKILL.md · Use when something non-trivial is to be built or reworked and its implementation plan has to be written, from an idea…
git:20261105.d17303e · audit A · 18 stars
write-plan SKILL.md skill
cliver-project/cliver · packages/cliver/src/cliver/skills/builtin/write-plan/SKILL.md · Create detailed, step-by-step implementation plans from design specs. Use after brainstorming or when you have a…
git:20261025.d71167b · audit A · 8 stars
write-plan SKILL.md skill
teambrilliant/dev-skills · skills/write-plan/SKILL.md · Write a technical implementation plan to thoughts/plans/ before coding starts (separate from the harness's plan mode)…
git:20261008.81e7416 · audit A · 5 stars
write-plan SKILL.md skill
hassan-mohiddin/freeflow · .skill-eval/qualification/subjects/neutral/write-plan/SKILL.md · Use when writing or revising an implementation plan, execution plan, remediation plan, migration plan, or similar…
git:20260718.e3de18c · audit A · 5 stars

Browse by kind, by grade A, or by owner.