review-docs

Batch and parallel review workflows scale documentation validation by launching one agent per document concurrently. This per-document coordination aggregates findings and prompts user approval before executing any archival or update actions.

Yes, you can validate architecture docs and specifications at scale by applying automated per-document agent assignments. Consolidated findings provide recommended actions before any archival or content updates occur.

The best way to check for outdated documentation is launching dedicated docs-curator agents that validate accuracy against the codebase, aggregating results to ensure alignment with implemented features before prompting user approval.

Yes, the documentation review process requires manual approval. It aggregates consolidated findings with recommended actions and prompts user approval before executing any archival or update actions on the reviewed documents.