change — Claude Code skill: what it does, how to install
change is a Claude Code skill that manages changes to a project already built with Briefproof and checks for regressions. It starts with /briefproof:change.
MIT ★ 132 updated 2026-11-09
/plugin marketplace add dmitribogatenkov/briefproof
/plugin install briefproof@briefproofWhat change does
The skill turns a change request into new requirements, a delta to the existing spec, and tickets for the affected work. After implementation, it checks the request and runs through the base run’s requirements to catch regressions.
The project needs a clean working tree and a completed Briefproof run. The skill reads the base spec and interfaces, then creates a separate folder for the change run. It leaves the base run untouched. Requests that grow into a redesign should start a new run with /briefproof:build.
The skill requires Claude Code and the plugin’s ledger tool, mcp__briefproof__state. An unfinished change run can resume with another /briefproof:change call.
What it helps with
- record new requirements for an existing project
- plan only the tickets affected by a change
- check that base requirements still hold
- catch regressions after implementation
Example prompts for the agent
- Change the signup form to collect a phone number, then check the existing requirements with
/briefproof:change. - Update CSV report export with
/briefproof:changeand check that the existing features still work.
How to install change
1Plugin marketplace
/plugin marketplace add dmitribogatenkov/briefproof/plugin install briefproof@briefproofThis installs the whole briefproof plugin with all its skills
2Skills CLI (Vercel)
npx skills add dmitribogatenkov/briefproof --skill change -a claude-code3Manually: put the files in place
~/.claude/skills/change/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/change/
1Skills CLI (Vercel)
npx skills add dmitribogatenkov/briefproof --skill change -a codex2Manually: put the files in place
.agents/skills/change/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dmitribogatenkov/briefproof --skill change -a cursor2Manually: put the files in place
.cursor/skills/change/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dmitribogatenkov/briefproof skills/change2Manually: put the files in place
.github/skills/change/SKILL.md1Skills CLI (Vercel)
npx skills add dmitribogatenkov/briefproof --skill change -a gemini-cli2Platform CLI
gemini skills install https://github.com/dmitribogatenkov/briefproof --path skills/changeManually: put the files in place
.devin/skills/change/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about change
How do I install change in Claude Code?
Add the marketplace with /plugin marketplace add dmitribogatenkov/briefproof, then install the plugin with /plugin install briefproof@briefproof.
What does change do?
It runs a focused change cycle for a project built with Briefproof: records new requirements, specifies the delta, plans affected tickets, and checks for regressions.
What does change require?
It requires Claude Code and the plugin ledger tool mcp__briefproof__state. The project folder must also have a completed Briefproof run.
Source text
SKILL.md · MIT
---
name: change
description: Changes a project that Briefproof already built, with the same discipline at small scale. The request becomes new quoted requirements, a spec delta, only the tickets that change, and a blind re-check of the request plus a regression pass over what the base run delivered. Starts only on /briefproof:change.
disable-model-invocation: true
argument-hint: "[auto|ask] what to change, in plain words"
---
# Briefproof · change request
**First, check you are in Claude Code.** This skill needs the plugin's ledger tool,
`mcp__briefproof__state`. If it is not available, tell the user in one line,
*"Briefproof runs in Claude Code: open the Code tab (local session) or a terminal
and run `/briefproof:change`"*, and stop.
A change request is a short Briefproof run on top of a finished one. Everything
in `/briefproof:build` still holds (read its five rules if you have not this
session): the request is quoted, never paraphrased; a stranger checks the result
against the words; no code before the spec delta; one fresh executor per ticket.
What differs is scope: you touch only what the request needs, and you prove the
rest still works.
## Start
```
state {action: "init", kind: "change", request: "<the user's words, verbatim>", mode: "ask"}
```
The ledger refuses when this folder has no finished run (tell the user to run
`/briefproof:build` for a new project, or `/briefproof:adopt` for one that
already exists) or when the run is unfinished (resume it instead). A finished
adoption is a base run like any other; its brief is what the project did when
it was adopted, and a requirement marked `broken` there is fair game for the
request.
On success it creates a new run folder, `{run}`, and names the base run,
`{base}`. The mod has already written:
- `{run}/1-brief/brief.md`: the base brief with a `## Change request` section
holding the request verbatim. This is the brief for this run.
- `{run}/1-brief/base-requirements.md`: what the base run delivered, for the
regression pass.
Read `{base}/4-spec/spec.md`, `{base}/4-spec/interfaces.md` and the project's
`AGENTS.md` before anything else. You are changing a known system, not
discovering one.
## Stages
The eight stages are the same and the pane shows them the same way; most are
shorter.
1. **Preflight.** Confirm the working tree is clean (commit or ask). `stage manifest`.
2. **Manifest.** `add_requirements` with verbatim quotes from the *change
request section only*. The base requirements are not re-added; they are the
regression list.
3. **Briefing.** Ask only what the request leaves open, one round, suggested
answer first, through `AskUserQuestion`. Often nothing.
4. **Spec.** Write `{run}/4-spec/spec.md` as a **delta**: start with one line
naming the base spec, then only the sections that change, each saying what it
replaces. Copy `{base}/4-spec/interfaces.md` to `{run}/4-spec/interfaces.md`
and amend it; never edit the base run's files. **Gate G2:** the coverage
checker reads `{run}/1-brief/brief.md` and the delta; tell it to check the
change request section against the delta.
5. **Plan.** Tickets for the change only, each naming the files it owns. If a
change touches a shared boundary, the three-ticket rule from the build skill
applies (add beside, migrate, remove). **Gate G3**, commit the plan.
6. **Build.** Waves, fresh executors, reviews where it pays, exactly as in the
build skill. Executors read `{run}/4-spec/interfaces.md`.
7. **Acceptance.** Clone to a temp dir and spawn the blind checker with
`prompts/acceptance.md`, giving it `{run}/1-brief/brief.md`,
`{run}/1-brief/base-requirements.md` and the clone. Tell it: *check every
sentence of the Change request section as the brief; then, for each line of
base-requirements.md, confirm it still holds with one quick check each and
report any that broke.* A broken base requirement is a fix ticket before
anything else. Save the reply as `{run}/7-acceptance/acceptance.md`. Then
record the evidence for each new requirement:
`set_requirement {id, status: "done", files: [<its FILES line>], note: "<evidence>"}`.
The pane watches those files afterwards, together with the base run's: when
this run finishes, the proof covers the whole chain. `gate G4`.
8. **Report.** `stage done` first, so the report and project memory are written
on the Done model; the mod rewrites the report page when this turn ends. Then
`{run}/8-report/report.md`: what changed and why, the new `R##` table, the regression result (N of N base requirements still hold), anything
deferred, and the usage table from `show`. Update `AGENTS.md` if how to run
or test changed.
## Red flags
- You edited a file under `{base}/`. Base runs are history.
- A base requirement broke and the report says "done" anyway.
- You rewrote the whole spec instead of a delta: the reader loses what changed.
- The request grew into a redesign. Say so, and offer `/briefproof:build` with a
new brief instead.
## Resume
A bare `/briefproof:change` with an unfinished change run in this folder: `show`,
re-read `{run}/1-brief/brief.md` and the current stage's files, continue.
© Dmitri Bogatenkov · MIT · dmitribogatenkov/briefproof