Write or refresh documentation for people from the project memory - architecture, onboarding, changelog, README - with every fact checked against the code
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Write Docs?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/antostr-write-docs)
---
name: write-docs
description: Write or refresh documentation for people from the project memory - architecture, onboarding, changelog, README - with every fact checked against the code
argument-hint: "[architecture | onboarding | changelog | readme | all]"
disable-model-invocation: true
---
Use the team skill to write documentation from the project memory: $ARGUMENTS
1. Read `docs/memory` (INDEX, STATE, MAP, the area cards, DECISIONS, PLAYBOOKS, ACCESS). If it
is missing, offer `/team:setup-memory` first; if it looks outdated, have `doc-keeper` fix it
before writing anything from it.
2. Agree what to write, where and in which language (AskUserQuestion; `ask_question` in agy):
architecture overview (for example `docs/ARCHITECTURE.md`), onboarding or contributing guide,
changelog from `STATE.md` and `git log`, README sections. Existing files are updated, not
replaced.
3. Run the assignment wizard for `technical-writer`.
4. Every fact comes from the memory and is checked against the code; every command shown is run
first. Nothing in the documentation may contradict the memory: if they disagree, the code
decides and the memory is corrected too.
5. Report the files written, what each covers, and the facts that could not be verified.
