review-docs

You can improve documentation quality by running parallel evaluations on style and content, tracking issues in a state file, and iterating through fixes until the document meets writing guidelines.

The best way to assess developer guides and user manuals is applying parallel evaluation agents that separately review style and content quality, maintaining a state file to surface and verify fixes iteratively.

To start evaluating API or internal documentation, provide the target document path as an argument to trigger the parallel evaluation workflow, which then assesses content and style while tracking issues for iterative improvement.

Yes, you can track documentation issues and verify fixes by maintaining a state file throughout the evaluation workflow, allowing you to monitor identified problems and confirm resolutions before completing the review.

Documentation review works for internal docs, developer guides, and user-facing content by applying structured quality assurance workflows that evaluate style and content in parallel to ensure comprehensive improvements.

Iterative documentation improvement workflows require user decisions to continue or finish the loop, meaning the process needs manual oversight and cannot fully auto-resolve complex writing guidelines or content gaps without human intervention.