planning-with-files SKILL.md skillA
planning-with-files in wpgaurav/wordpress-skills is at git:20261024.783ca3d (Oct 24, 2026), graded A.
mdr add wpgaurav/wordpress-skills/planning-with-files@git:20261024.783ca3dThis 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.
planning-with-files from bg-szy/top-skills 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
- bg-szy/top-skills
- Path
skills/Claude-meta-skill/planning-with-files/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260522.3711c9f, committed May 22, 2026
- Size
- 3,876 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
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
# Planning with Files Work like Manus: Use persistent markdown files as your "working memory on disk." ## Quick Start Before ANY complex task: 1. **Create `task_plan.md`** in the working directory 2. **Define phases** with checkboxes 3. **Update after each phase** - mark [x] and change status 4. **Read before deciding** - refresh goals in attention window ## The 3-File Pattern For every non-trivial task, create THREE files: | File | Purpose | When to Update | |------|---------|----------------| | `task_plan.md` | Track phases and progress | After each phase | | `notes.md` | Store findings and research | During research | | `[deliverable].md` | Final output | At completion | ## Core Workflow ``` Loop 1: Create task_plan.md with goal and phases Loop 2: Research → save to notes.md → update task_plan.md Loop 3: Read notes.md → create deliverable → update task_plan.md Loop 4: Deliver final output ``` ### The Loop in Detail **Before each major action:** ```bash Read task_plan.md # Refresh goals in attention window ``` **After each phase:** ```bash Edit task_plan.md # Mark [x], update status ``` **When storing information:** ```bash …
Read the whole file at its exact version.
How to install
mdr add bg-szy/top-skills/planning-with-files@git:20260522.3711c9fPins git:20260522.3711c9f in mdr.lock, 1 version behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_p4zxaijx76j4qlb6/0b3ba3c6d148704019fdc91474bb501ae993763843dd06c7a0c3daf8fcc208d6.json
Then /plugin install planning-with-files@markdownregistry-p4zxaijx76j4qlb6 in Claude Code. It installs git:20260522.3711c9f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add bg-szy/top-skills/planning-with-files@sha256:0b3ba3c6d1487040The older copy line above pins the label git:20260522.3711c9f, 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_p4zxaijx76j4qlb6)
2 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 wpgaurav/wordpress-skills/planning-with-files, and what changed since 0b3ba3c? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of planning-with-files from somewhere else? Ask it: where did my planning-with-files 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 May 22, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20261024.783ca3d of planning-with-files in wpgaurav/wordpress-skills (skills/tools/planning-with-files/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260330.1e42c4b, which it committed on Mar 30, 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/planning-with-files/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 (3876 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
bg-szy/top-skills · 6 stars · license a license file GitHub does not identify · pushed 2026-11-15 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_p4zxaijx76j4qlb6 GET https://markdownregistry.com/api/v1/resolve?ref=bg-szy/top-skills/planning-with-files GET https://markdownregistry.com/api/v1/blob/0b3ba3c6d148704019fdc91474bb501ae993763843dd06c7a0c3daf8fcc208d6
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 bg-szy/top-skills
Every file in bg-szy/top-skills