Documentation Skill

Goal

Keep documentation synchronized with the project state. Treat stale documentation as a project bug, but do not create documentation churn for internal-only changes that do not affect users, operators, contributors, architecture, or future agents.

Default Workflow

1. Inspect relevant existing documentation before editing docs, and before code changes when docs may influence the implementation.
2. Identify whether the task changes interface, structure, or project knowledge.
3. Make the code or project change.
4. Verify the actual change by reading the modified files or running git diff. Do not rely on memory of what was just done.
5. Update only the affected documentation, grounded in what step 4 revealed.
6. Check for contradictions between code, README, docs, changelog, and agent guidance.
7. Summarize documentation work in the final response.

Decide Whether To Update Docs

Always check for documentation impact. Update docs only when at least one answer is "yes":