# Document After Change

> Update a project's README and the relevant vault notes (overview / module map) after a meaningful code change — new feature, new file, new module, or an architectural decision. Should trigger on its own once a coding task is finished, without the user having to ask — skip it for trivial (typo/formatting) changes. Also runs manually when the user says "update the docs" or "document this.

- **Type:** Skill
- **Install:** `agentstack add skill-cormff-claude-code-playbook-document-after-change`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [cormff](https://agentstack.voostack.com/s/cormff)
- **Installs:** 0
- **Category:** [Security](https://agentstack.voostack.com/c/security)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [cormff](https://github.com/cormff)
- **Source:** https://github.com/cormff/claude-code-playbook/tree/main/skill-tree/layer-3-maintenance/document-after-change

## Install

```sh
agentstack add skill-cormff-claude-code-playbook-document-after-change
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Document After Change

Code and documentation drift apart the moment documentation becomes a separate, remembered step instead of part of finishing the task. This skill is meant to close that gap automatically.

## When this should fire

- A new feature, file, or module was added.
- An architectural decision was made or changed.
- A module's behavior changed enough that its existing documentation is now wrong.

## When to skip

Trivial changes — typo fixes, formatting, comment-only edits — don't need this.

## What to update

1. **The project's README**, if the change affects how the project is used, built, or structured.
2. **The relevant vault note(s)** — the project overview if architecture changed, the specific file/module map (see [`vault-format`](../../layer-0-foundation/vault-format/SKILL.md#functionmodule-map-structure-for-code-projects)) if a file's functions changed.
3. **The project hub**, if a new note was created and needs to be linked in.

## Don't scope-creep

This skill documents what changed — it isn't an invitation to refactor unrelated documentation or expand scope beyond the actual change. If the existing docs have unrelated problems, note them separately rather than fixing them inside this pass.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [cormff](https://github.com/cormff)
- **Source:** [cormff/claude-code-playbook](https://github.com/cormff/claude-code-playbook)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-cormff-claude-code-playbook-document-after-change
- Seller: https://agentstack.voostack.com/s/cormff
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.