knowledge-integrator

To synchronize project documentation with architectural decisions, this Skill identifies structural changes in chat, scans root README.md, CLAUDE.md, and docs/ directories for impacted files, and proposes precise diff updates for explicit approval before applying any edits.

A Knowledge Integration Alert is a structured governance output that surfaces before and after diff proposals for impacted documentation, ensuring architectural changes, business pivots, and rule updates require explicit approval before source-of-truth files are modified.

To propose diffs after a business pivot, state the decision change and the Skill will locate affected documentation in architecture/ and specs directories, producing a structured Knowledge Integration Alert with exact before/after proposals awaiting your review.

No, this docs-sync approach does not automatically modify files; it cross-discovers impacted locations in CLAUDE.md and architecture/ directories, then awaits explicit approval before applying any proposed diff changes to the project.

The best way to prevent docs drift is using proactive documentation synchronization to detect decisions in chat, scan common documentation locations for impacted files, and surface exact update proposals in a structured alert format for governance review.

You need to scan for impacted documentation files after new personas or rule updates when structural decisions are established in chat, requiring cross-file discovery across specs and docs/ to align the project's source-of-truth documentation.