executing-plans SKILL.md skillA
executing-plans in chinkan/rustfox is at git:20260408.ae338c2 (Apr 8, 2026), graded A.
mdr add chinkan/rustfox/executing-plans@git:20260408.ae338c2This copy is 1 version behind it. See what changed · install this older copy instead
This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.
executing-plans from neversight/learn-skills.dev is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- neversight/learn-skills.dev
- Path
data/skills-md/0x2e/superpowers/executing-plans/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260313.97f6d01, committed Mar 13, 2026
- Size
- 2,550 bytes
- Repository stars
- 223
- License
- none declared
Use when you have a written implementation plan to execute in a separate session with review checkpoints.
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
# Executing Plans ## Overview Load plan, review critically, execute tasks in batches, report for review between batches. **Core principle:** Batch execution with checkpoints for architect review. **Announce at start:** "I'm using the executing-plans skill to implement this plan." ## The Process ### Step 1: Load and Review Plan 1. Read plan file 2. Review critically - identify any questions or concerns about the plan 3. If concerns: Raise them with your human partner before starting 4. If no concerns: Create TodoWrite and proceed ### Step 2: Execute Batch **Default: First 3 tasks** For each task: 1. Mark as in_progress 2. Follow each step exactly (plan has bite-sized steps) 3. Run verifications as specified 4. Mark as completed ### Step 3: Report When batch complete: - Show what was implemented - Show verification output - Say: "Ready for feedback." ### Step 4: Continue Based on feedback: - Apply changes if needed - Execute next batch - Repeat until complete ### Step 5: Complete Development After all tasks complete and verified: - Announce: "I'm using the finishing-a-development-branch skill to complete this work." …
Read the whole file at its exact version.
How to install
mdr add neversight/learn-skills.dev/executing-plans@git:20260313.97f6d01Pins git:20260313.97f6d01 in mdr.lock, 1 version behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ji6gan3lbmvb3rij/d099fa42fd7518f4dafa9f2d51c1c08fce970490d57682b6acd3e7a57bb55b52.json
Then /plugin install executing-plans@markdownregistry-ji6gan3lbmvb3rij in Claude Code. It installs git:20260313.97f6d01, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add neversight/learn-skills.dev/executing-plans@sha256:d099fa42fd7518f4The older copy line above pins the label git:20260313.97f6d01, 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_ji6gan3lbmvb3rij)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest chinkan/rustfox/executing-plans, and what changed since d099fa4? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of executing-plans from somewhere else? Ask it: where did my executing-plans 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 1 version of this file, committed on Mar 13, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20260408.ae338c2 of executing-plans in chinkan/rustfox (.claude/skills/executing-plans/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260216.154b1fd, which it committed on Feb 16, 2026, before this repository did; graded A, 1 version behind.
See what changed since these bytes · ask your agent
Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.
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/executing-plans/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 (2550 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
neversight/learn-skills.dev · 223 stars · license none declared · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ji6gan3lbmvb3rij GET https://markdownregistry.com/api/v1/resolve?ref=neversight/learn-skills.dev/executing-plans GET https://markdownregistry.com/api/v1/blob/d099fa42fd7518f4dafa9f2d51c1c08fce970490d57682b6acd3e7a57bb55b52
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 neversight/learn-skills.dev
Every file in neversight/learn-skills.dev