1natsu-document-harness

To keep documentation aligned with code changes automatically, you can use a documentation harness that analyzes git diff and log outputs to identify impacted packages, then orchestrates updates across CLAUDE.md, .claude/rules/, docs/, and feature READMEs to reflect the current implementation.

The best way to update CLAUDE.md and feature READMEs post-implementation is to run an automated documentation workflow that surveys existing docs first, adjusts references to avoid duplication, and only creates new documentation files when structurally required.

A documentation harness maintains consistency by surveying existing documentation structure, tone, and references across multiple directories, applying change-scoping and consistency checks to ensure all artifacts accurately reflect the latest architecture updates without duplication.

You do not need to manually scope documentation updates for new features, as the harness automatically outlines steps for change-scoping by analyzing git history to determine impacted packages, directories, and artifacts like plan files and design memos.

You should avoid creating new documentation files when existing docs can be updated to reflect the code changes, as the harness prioritizes refreshing existing references in CLAUDE.md and docs/ first, generating new files only when absolutely required.