doc-sync

Documentation drift is reduced by reading git status and parsing _targets.R to detect implementation changes, then minimally updating CLAUDE.md status files and appending structured delta logs for human review.

To update CLAUDE.md after R targets change, run a sync pass that scans your project directories and applies minimal edits to Tier 1 context files to reflect updated stage gates and active pipeline targets.

Yes, this Skill works with Quarto notebooks and R targets pipelines by parsing _targets.R, scanning notebooks/ and R/ directories, and updating Tier 1 context files to reflect the current research codebase state.

The best way to log specification deltas is appending structured entries to docs/deltas.md when implementation reveals corrections or new constraints, ensuring human review without directly editing Tier 2 specification files.

You should avoid automated documentation updates for Tier 2 specification files, as the Skill enforces tiered safety rules that never edit specifications directly and instead nudges strategy reconciliation when unresolved deltas accumulate.