docs-analysis

Documentation synchronization is achieved by tracing links from modified code to files under the docs/ directory, mapping impacted API and architecture documents, and treating required documentation updates as part of the same iteration.

Documentation context discovery involves reading and summarizing files under the docs/ directory to extract business, architecture, and API context before beginning feature work or refactoring.

Identify affected documents by tracing code changes to linked files in the docs/ directory, then prioritize updates based on modified APIs, schemas, workflows, and architecture to ensure technical writing remains accurate.

Yes, you can enforce documentation maintenance as a quality gate by treating documentation updates as part of the same iteration and marking tasks complete only when related docs are verified and updated within the docs directory.

The best way to map impacted architecture documentation is to analyze the docs/ directory, trace dependencies between modified code and architecture documents, and produce a prioritized list of required documentation updates.

Project documentation lags behind implementation decisions when updates are not enforced within the same iteration as API changes, creating synchronization gaps between actual code behavior and written technical context.