Document

Document

Module specified

1. Find all docs mentioning the module
2. Update for accuracy against current code
3. Align terminology across files
4. Add or refresh docs/status/[module]-status.md if the project uses status docs
5. Update public API docs (OpenAPI, typedoc, rustdoc) when the project maintains them

organize (or whole docs tree)

1. Scan for overlap — merge or cross-link when >50% duplicate
2. Archive obsolete docs if the project has an archive/ convention
3. Fix broken links and index files (README, DOCUMENT-INDEX, etc.)
4. Ensure each doc has a Related or navigation section if that is the norm
5. Accuracy pass — signatures, CLI flags, env vars, test counts vs real code
6. Report: merged, archived, fixed, still stale

No docs tree yet

If the project has no docs/ but needs one, propose a minimal layout (README index + module page) — do not create sprawl without user approval.

Always

• Document only what exists — no wishlist features
• Prefer updating existing docs over sprawl

Related skills

• audit — status docs and gap tables
• release — changelog and release docs
• discover-project — find docs layout and conventions