update-docs

To audit and update documentation, use a structured six-phase workflow that inventories primary, architecture, knowledge-base, and reference docs, requires plan approval before applying changes, and enforces cross-document consistency checks.

Keeping project docs in sync requires cross-document consistency checks across primary, architecture, knowledge-base, and reference docs, applying external doc-sync reminders and inventory updates after a user-approved plan.

Yes, you can review a documentation update plan before changes are applied; the workflow enforces explicit user approval prior to edits, ensuring you validate all planned updates across the documentation inventory.

Removing outdated content from a knowledge base and reference docs is handled by auditing existing files, identifying stale information, and applying structured updates through a six-phase workflow with plan-based execution.

Yes, the documentation update workflow operates on CLAUDE.md, docs/, and knowledge-base copies, auditing all primary, architecture, knowledge-base, and reference docs to ensure accuracy and external reference synchronization.

A limitation of plan-based execution for documentation audits is that no edits occur until explicit user approval is granted during the workflow, meaning changes are paused if approval is delayed or withheld.