plan SKILL.md skillA
plan from procoders/superpowers-v is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add procoders/superpowers-v/plan@git:20261022.cf63e43Pins git:20261022.cf63e43 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- procoders/superpowers-v
- Path
skills/plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261022.cf63e43, committed Oct 22, 2026
- First version recorded
- Oct 22, 2026
- Size
- 9,168 bytes
- Repository stars
- 42
- License
- MIT
How a Compound V plan is written. The compound-v:builder follows it after its own research, and Claude can load it directly to write or revise a plan. Writes the implementation plan with an acceptance table (behaviour → check), the four checklists answered item by item, tasks with their tests, a task → model table, lanes only for parallel work, and the machine-readable compound-v-plan block. Then attaches it to the run record.
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
A plan is the set of decisions a build cannot make on the fly: which files, which behaviours, which checks prove them. The `compound-v:builder` writes it, after its own domain research and code reading, and then builds from it. Write it for an engineer who has not seen the brainstorm. The acceptance table is the contract that both the build and the review are held to.
All `compound-v.py` calls below are `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/compound-v.py" …` with the run's `--id <id>` (the session brief prints it as `Compound V run <id>` if you lost it).
**Commands.** Run each command as one plain command line with literal values (the run id, real paths): no shell variables you set yourself, no `;` or `&&` chains, no `$?`, and no pipes or redirects (`|`, `>`, `2>&1`): the one exception is the `<<'REQUEST'` heredoc that hands `run start` its request. The sandbox's auto-allow refuses compound commands, and `sandbox.excludedCommands` only matches a bare call.
## 0. Inputs
…Read the whole file at its exact version.
How to install
mdr add procoders/superpowers-v/plan@sha256:b0d7a0ca8b6f90b5The line at the top of this page pins the label git:20261022.cf63e43, 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_7jqjm36zvuf3xzs2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 22, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.cf63e43 latest | 2026-10-22 | cf63e43 | 9,168 B | A | view · diff |
| git:20261022.bfb73d4 | 2026-10-22 | bfb73d4 | 9,019 B | A | view · diff |
| git:20261022.5278845 | 2026-10-22 | 5278845 | 8,831 B | A | view · diff |
| git:20261022.500596a | 2026-10-22 | 500596a | 8,837 B | A | view · diff |
| git:20261022.33a216e | 2026-10-22 | 33a216e | 8,616 B | A | view |
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 (9168 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
procoders/superpowers-v · 42 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7jqjm36zvuf3xzs2 GET https://markdownregistry.com/api/v1/resolve?ref=procoders/superpowers-v/plan GET https://markdownregistry.com/api/v1/blob/b0d7a0ca8b6f90b571d42a9a4c84777ae999283dcdaca9b38bee86095e492fa6
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 procoders/superpowers-v
Every file in procoders/superpowers-v