What it does
Use it whenever a code change, incident, migration, or architectural decision should leave behind durable written context instead of living only in chat history.
How it works
- Figures out what must be documented and where it belongs in the repo.
- Converts execution details into concise docs, procedures, notes, or reports.
- Optimizes for future maintainers: what changed, why, how to verify, and how to repeat it.
Best for
- • Runbooks and implementation notes
- • Architecture and decision docs
- • Post-fix writeups
Expected outputs
- • Repo-ready documentation artifact
- • Operational or architectural context
- • Readable change explanation close to the code