ct-docs-sync

Documentation drift is detected by running a bash script that compares source truth files against user-facing references. The skill reads core files under scripts/ and docs/ to report mismatches across COMMANDS-INDEX.json, README, and vision documents.

Documentation drift happens when canonical docs become inconsistent with implemented commands and system architecture. You need to check for it during development and release cycles to ensure documentation accuracy for both users and agent workflows.

Yes, jq is required to run the bash documentation validation scripts. It is the only dependency needed to execute the drift detection process and parse the JSON configuration files.

Drift detection checks are configured using a drift-config.json file. This file defines the specific validation rules that the bash script uses to align source truth with developer and user-facing documentation.

The best way to keep documentation aligned is running automated drift detection across scripts, indices, and vision documents. This ensures a single source of truth and provides automated guidance to remediate discrepancies before releases.