doc-update

To plan documentation updates after a code migration, you generate a structured plan that reads referenced files, analyzes impact, and maps changes to the documentation hierarchy with absolute file paths and rationales. This ensures module docs and root docs accurately reflect system evolution.

Documentation gap analysis is the process of identifying missing documentation, outdated references, and alignment gaps between implementation and docs. You need it when code changes, feature additions, or policy updates occur to ensure technical writing remains accurate and self-sufficient.

Yes, you can map implementation changes to existing architecture notes without editing code. The process reads referenced files and provides absolute file references to cross-reference implementation updates with the documentation hierarchy while preserving versioning considerations.

To ensure your README and API docs reflect recent feature additions, generate a documentation update plan that cross-references implementation changes across modules. This produces absolute file paths and rationales to guide updates across all affected technical documentation.

The best way to align technical documentation with system evolution is performing a documentation audit that identifies alignment gaps between implementation and docs. This generates a structured update plan covering root docs, module docs, and architecture notes without modifying code.

No, you do not need to manually check every file when coordinating policy change updates. The system reads referenced files automatically, analyzes the impact of changes, and produces a structured plan with rationales to update affected modules and root documentation efficiently.