doc-sync

To synchronize CLAUDE.md and README.md documentation and prevent drift, run a phase-based workflow that detects outdated indexes, migrates misplaced architectural content to README.md, and updates index tables. This ensures consistent repository context for both LLM agents and humans.

Documentation drift detection identifies misplacements where architectural content incorrectly resides in CLAUDE.md instead of README.md, and flags missing or outdated table-based indexes. It audits the hierarchy to guarantee LLM agents receive accurate, intended architectural knowledge.

Yes, you can audit documentation hierarchy for specific directories instead of the whole repository. The synchronization process supports scope flexibility, allowing targeted discovery, drift detection, and index updates tailored to directory-specific onboarding or refactoring efforts.

To migrate architectural content from CLAUDE.md to README.md safely, the workflow moves designer notes during its migration phase, then applies a verification step. It reports the changes to ensure README.md contains the intended knowledge without data loss.

CLAUDE.md requires a strict table-based format for documentation synchronization. The process imposes this structure and validates that targeted directories have up-to-date indexes matching the table format before completing its verification phase.

CLAUDE.md documentation synchronization may fail during index updates if the existing CLAUDE.md format does not use the required table-based structure, or if targeted directories lack the necessary up-to-date indexes needed to pass the final verification phase.