docs-refresh

Automating documentation hygiene involves running periodic staleness scans across project memory, CLAUDE.md, and docs vaults to surface outdated content. The docs-refresh workflow orchestrates this inventory, triage, and cleanup process automatically.

Triage outdated project docs by identifying candidates for deletion or update, then applying consistent compression and archiving. This automated triage step ensures decision records and memory notes remain accurate and actionable during major architecture changes.

A staleness scan for a docs vault works by inventorying existing documentation, memory notes, and lessons, then assessing content drift over time. It flags dead or outdated content for triage, execution, and verification during maintenance cycles.

You need to run a documentation refresh workflow during periodic maintenance cycles, after major architecture changes, or during post-release reviews. These are the critical points where documentation drift typically occurs and automated hygiene is required.

Yes, you can use automated docs inventory for post-release reviews to detect documentation drift. The workflow scans memory, CLAUDE.md, and the docs vault to identify outdated content, prune dead entries, and verify knowledge reliability.

Archive outdated memory notes by identifying triage candidates and applying consistent compression before moving them to an archive. This preserves project context while ensuring active memory, CLAUDE.md, and docs remain fresh and actionable.