devlyn:update-docs

To synchronize documentation with code while preserving roadmaps, run a full-repo doc audit that compares existing docs against the codebase, flags ambiguous future material, and applies structured edits without deleting visions, RFCs, or open questions.

The best way to clean up stale project documentation is performing a gap analysis that inventories all docs, categorizes their freshness, removes completed TODOs, deletes dead references, and fixes cross-document inconsistencies.

No, updating documentation does not remove future-facing architectural proposals. The process safeguards ADRs, RFCs, visions, and open questions by flagging ambiguous items instead of silently deleting them during synchronization.

To find outdated or missing documentation across your repository, execute a documentation inventory and gap analysis that locates all docs, categorizes their accuracy against the current codebase, and identifies areas needing updates.

Yes, you can update developer references for specific features without scanning the entire codebase by running focused documentation updates that target individual evolving features while still applying safety rules to preserve future-oriented content.

If your docs contain cross-references that no longer exist in the code, run a documentation synchronization process that fixes cross-document inconsistencies and deletes dead references while preserving any remaining roadmap or decision content.