vibe-change-spec SKILL.md skillA
vibe-change-spec from aakashdhar/vibe-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aakashdhar/vibe-skill/vibe-change-spec@git:20261030.c951717Pins git:20261030.c951717 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aakashdhar/vibe-skill
- Path
vibe-change-spec/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261030.c951717, committed Oct 30, 2026
- First version recorded
- Apr 17, 2026
- Size
- 34,840 bytes
- Repository stars
- 7
- License
- none declared
Scope change workflow for modifying, adding, or removing requirements at any point during a build. Triggers on "change:" prefix, "I forgot to add", "actually I also want", "can we add", "remove X from scope", "I changed my mind about", "before we continue add", "one more thing", "I want to change the spec", "revert the X change". Handles new additions, removals, renames, backlog operations, and reverting previous changes. Assesses impact before touching any file. Updates all affected docs…
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
# Vibe Change Spec Skill Handles scope changes at any point during the build: safely, in the right order. Always assesses impact first. Always waits for confirmation. Never edits files speculatively. Every reviewed document it changes is reviewed again, independently, before anything is built from it. **No application code. The only files this skill writes are:** `BRIEF.md`, `ARCHITECTURE.md` (root or `vibe/`), `vibe/SPEC.md`, `vibe/SPEC_INDEX.md`, `vibe/PLAN.md`, `vibe/TASKS.md`, `vibe/DECISIONS.md`, `vibe/CODEBASE.md`, `vibe/backlog/*.md`, the FEATURE_SPEC.md / FEATURE_PLAN.md / FEATURE_TASKS.md of the feature folders the change touches, and the spec and design gates (`vibe/.gates.json`, through `vibe_state.py`). The review it runs (vibe-spec-review → vibe-goldfish) writes its own records under `vibe/goldfish/` and `vibe/spec-reviews/`. > **Autonomous / headless mode.** At startup resolve the settings with > `python3 ~/.claude/skills/vibe-mode/scripts/vibe_state.py mode` (`mode --run` when the > caller says this skill was entered from `vibe-mode: run`, which forces autonomous). If …
Read the whole file at its exact version.
How to install
mdr add aakashdhar/vibe-skill/vibe-change-spec@sha256:4a8a1e72b9c9a585The line at the top of this page pins the label git:20261030.c951717, 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_bkmtq6vtxfujeada)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 17, 2026 and Oct 30, 2026, about one every 49 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261030.c951717 latest | 2026-10-30 | c951717 | 34,840 B | A | view · diff |
| git:20261030.a66992c | 2026-10-30 | a66992c | 13,856 B | A | view · diff |
| git:20260923.02e1108 | 2026-09-23 | 02e1108 | 13,808 B | A | view · diff |
| git:20260910.fc4ff2b | 2026-09-10 | fc4ff2b | 13,285 B | A | view · diff |
| git:20260417.e152a1c | 2026-04-17 | e152a1c | 13,226 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 (34840 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
aakashdhar/vibe-skill · 7 stars · license none declared · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bkmtq6vtxfujeada GET https://markdownregistry.com/api/v1/resolve?ref=aakashdhar/vibe-skill/vibe-change-spec GET https://markdownregistry.com/api/v1/blob/4a8a1e72b9c9a5853360871ae0ee2b33c08c0435f58d33833bb93483ffedc79a
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.