| name | doc-writer |
| description | Generate and update technical documentation — architecture, conventions, design decisions, changelogs |
| version | 2.0.0 |
| compat | claude-code, codex, cursor, openclaw |
Skill: doc-writer
What it does
Generates and updates technical project documentation: architecture, conventions, design decisions, and changelogs.
When to use it
- After completing a project or major feature
- When
.knowledge/ is out of sync with the actual code
- When a new agent needs project context
Files it generates or updates
.knowledge/README.md — project overview
.knowledge/architecture.md — technical decisions and structure
.knowledge/conventions.md — code patterns, naming, folder structure
CHANGELOG.md — versioned change history
Process
- Read the current code (folder structure, key files)
- Compare with existing
.knowledge/
- Update only what changed, don't rewrite from scratch
- Maintain a technical, concise tone — these docs are read by agents, not humans
Expected output
.md files updated with last modification date in the header.
Warnings
- Don't invent unimplemented behaviors
- If there's ambiguity, document what's in the code, not what should be
- Keep
.knowledge/ as the source of truth — don't duplicate in /docs