gza-docs-review

To review documentation for completeness, run a structured process that discovers core docs, verifies them against the implementation, performs gap analysis, and generates a templated findings report to bridge missing information.

Documentation gap analysis systematically scans core docs like README and API references to identify missing information and inaccuracies, ensuring documentation remains accurate, complete, and useful for onboarding new users and maintaining adoption.

Yes, you can check documentation consistency across multiple components by applying a structured review process that reads project docs, verifies alignment with the implementation, and reports inconsistencies to guide maintainers in correcting errors.

Yes, the documentation review process works for onboarding new users by systematically verifying that Quick Start and Configuration docs are complete, accurate, and aligned with actual implementation and user needs.

The best way to maintain up-to-date project docs is to run systematic reviews that verify documentation against the implementation, perform consistency checks, and generate templated reports to guide authors in closing gaps and correcting errors.