plan SKILL.md skillA
plan from vibemaestro/vibemaestro-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vibemaestro/vibemaestro-kit/plan@git:20261113.9661a88Pins git:20261113.9661a88 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vibemaestro/vibemaestro-kit
- Path
plugins/vibemaestro-sdlc/skills/plan/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261113.9661a88, committed Nov 13, 2026
- First version recorded
- Oct 22, 2026
- Size
- 12,035 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use when: a topic needs two or more PRs (or a new PR is decided for a topic that has a plan), or someone asks what the state of a topic is — after a shallow recon of the current state, write or extend kb/plans/<date>-<slug>.md (one row per PR: how, the AC it delivers, depends on, trust touches, link, a version on a group's release row only; the owner's decisions verbatim; a living plan), link each dispatched intent to its row, and read the live state with kb.py plan status instead of…
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
# plan — the plan of a topic that takes several PRs One intent = one branch = one PR = one session. A topic too big for one PR is split across PRs, and the plan is the one place that split lives: how each PR builds it, which AC of the story it delivers, what it waits for, what needs a signature, which release row ships it, and what the owner decided. The what and the acceptance live in the spec; the plan holds the how. Its state is read from GitHub by a command, never written into the plan, so a later session answers "where is this topic?" from one file and one command instead of re-reading issues, PRs, comments and specs. ## When - **A topic needs 2 or more PRs:** write its plan before work on the second PR starts. A single-PR intent needs no plan. - **A topic has a plan and a new PR is decided:** add a row. **A PR is dropped:** write `dropped: <reason>` in its Link cell. - **Someone asks what the state of a topic is:** run `kb.py plan status` on its plan (below) and read the plan; open an issue, PR or spec only for what the status flags. ## Recon, before rows are written or extended …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rdks5uflkj72a2x2/245fbf9bfea1132c67f9390125e77ef9732b79723c28ec72ed9b1c9997d8cb9e.json
Then /plugin install plan@markdownregistry-rdks5uflkj72a2x2 in Claude Code. It installs git:20261113.9661a88, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vibemaestro/vibemaestro-kit/plan@sha256:245fbf9bfea1132cThe line at the top of this page pins the label git:20261113.9661a88, 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_rdks5uflkj72a2x2)
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: what changed in vibemaestro/vibemaestro-kit/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 plan from somewhere else? Ask it: where did my 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 4 versions of this file, between Oct 22, 2026 and Nov 13, 2026, about one every 7 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.9661a88 latest | 2026-11-13 | 9661a88 | 12,035 B | A | view · diff |
| git:20261031.04472f5 | 2026-10-31 | 04472f5 | 10,074 B | A | view · diff |
| git:20261029.d5142f7 | 2026-10-29 | d5142f7 | 9,834 B | A | view · diff |
| git:20261022.867b0e0 | 2026-10-22 | 867b0e0 | 7,830 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/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 (12035 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
vibemaestro/vibemaestro-kit · 4 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rdks5uflkj72a2x2 GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/plan GET https://markdownregistry.com/api/v1/blob/245fbf9bfea1132c67f9390125e77ef9732b79723c28ec72ed9b1c9997d8cb9e
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 vibemaestro/vibemaestro-kit
Every file in vibemaestro/vibemaestro-kit