Documentation
Use this skill when you need to explain verified behavior, update guides, or keep delivery notes in sync with the code.
Core Rules
- Document only what you can verify in the repo.
- Prefer file links and concrete examples over broad prose.
- Update related docs when names, flows, or interfaces move.
- Remove stale content when it becomes misleading.
Outputs
- Updated docs outline
- Cross-reference checklist
- Staleness notes
Source: Zakarialabib/opencode — distributed by TomeVault.