spec SKILL.md skillA
spec 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/spec@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/spec/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261113.9661a88, committed Nov 13, 2026
- First version recorded
- Oct 22, 2026
- Size
- 9,373 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use when: the intent of an app repo is recorded (kb/intent/<date>-<slug>.md, branch intent/<date>-<slug>) and there is no approved spec yet — create kb/specs/<date>-<slug>.md in the spec shape (goal, constraints, behaviour-level criteria pointing to the story's AC, risks to cover, open points), commit it to the intent branch, then ask for approval (session-ask in a sandbox, ask directly in a solo session) BEFORE editing code.
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
# spec — derive the spec from the intent and get it approved before code
The intent says **what the person wants** (for a story: the story the owner approved); the spec says **what must be true**, as
behaviour, derived from it, and which risks the tests must cover. It holds no implementation: the how belongs to the plan
(`vibemaestro-sdlc:plan`) or to the session's own judgement. The spec is approved **before** the first line of code: approving two
pages is much cheaper than reviewing a PR built in the wrong direction. Who approves: in a coordinated session the coordinator;
the owner is asked only when the spec would change an AC of the story. In a solo session the person approves the story and the
spec in one ask. The spec shape is the one recorded in this repo's own `kb/README.md` (built by `init-kb`).
Condition: an intent exists (`vibemaestro-sdlc:intake`) and you stand in the worktree of the branch `intent/<date>-<slug>`.
If not, do `intake` first.
## Do
1. **Create the skeleton file** — the same `<date>-<slug>` as the intent, so the two files go as a pair:
```bash
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb.py" new spec <slug> --date <date>
```
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_rg5e4nzeifxio6zm/3f1bf28d191659a8e94df7523c5e46006454052699b052afad5972bbdc73ffa6.json
Then /plugin install spec@markdownregistry-rg5e4nzeifxio6zm 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/spec@sha256:3f1bf28d191659a8The 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_rg5e4nzeifxio6zm)
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/spec 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 spec from somewhere else? Ask it: where did my spec 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 22, 2026 and Nov 13, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.9661a88 latest | 2026-11-13 | 9661a88 | 9,373 B | A | view · diff |
| git:20261103.f4a254c | 2026-11-03 | f4a254c | 9,452 B | A | view · diff |
| git:20261031.04472f5 | 2026-10-31 | 04472f5 | 7,347 B | A | view · diff |
| git:20261029.d5142f7 | 2026-10-29 | d5142f7 | 5,963 B | A | view · diff |
| git:20261022.867b0e0 | 2026-10-22 | 867b0e0 | 5,779 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/spec/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 (9373 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_rg5e4nzeifxio6zm GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/spec GET https://markdownregistry.com/api/v1/blob/3f1bf28d191659a8e94df7523c5e46006454052699b052afad5972bbdc73ffa6
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