ce-compound-refresh

To refresh stale documentation, audit learnings and pattern docs against the current codebase to detect drift, then apply targeted actions like update, consolidate, replace, or delete to keep docs accurate.

Documentation drift occurs when learnings and pattern docs become outdated relative to the codebase. You identify drift by auditing file references, frontmatter, and code context to flag inconsistencies during maintenance.

To clean up duplicate and obsolete learnings, execute a drift-aware audit across multiple topics that consolidates overlapping content, replaces outdated guidance, and deletes obsolete files while generating a structured report.

Run a documentation maintenance audit when drift is flagged during routine maintenance, immediately after significant code changes, or when users request a cleanup of stale docs to ensure guidance remains accurate.

Yes, the documentation refresh workflow scales across multiple topics by analyzing frontmatter, file references, and code context, executing drift-aware actions, and recording a provenance trail for review.