ce-compound-refresh

Documentation drift detection is performed by reviewing learnings in docs/solutions/ to surface stale patterns and outdated code references. It compares documented learnings against the current codebase to identify missing consolidation opportunities and classify drift.

Maintaining pattern doc accuracy requires refreshing or consolidating derived documentation to reflect new code, migrations, or refactors. The process generates an applicability report detailing applied changes and recommended actions like updating references or replacing obsolete artifacts.

Consolidating outdated solution docs involves reviewing existing learnings for drift, then replacing them with canonical successors or deleting obsolete artifacts. It classifies drift through evidence gathering and outputs a final report of recommended consolidation actions.

Automated documentation maintenance is needed when you have a docs/solutions/ directory containing accumulated learnings that must be reviewed against codebase changes. It preserves accuracy and usability by flagging outdated references and applying necessary updates after migrations or refactors.

Generating a report of recommended actions for stale documentation is a core output of the drift review process. The final applicability report explicitly details both applied changes and recommended actions, covering reference updates, doc consolidation, and artifact deletion.

The ce-compound-refresh process requires no external dependencies to run. It operates directly on your docs/solutions/ directory using built-in references and assets to classify drift and generate recommended maintenance actions.