doc-reviewer

To review documentation quality automatically, run the /doc-reviewer command to detect Markdown files under docs/ and generate a structured critique on completeness, clarity, consistency, and maintainability.

To evaluate architecture and PRD documents for completeness, use automated documentation review to classify files into categories like ARCHITECTURE and PRD, applying targeted review criteria to generate actionable improvement recommendations.

Yes, you can check consistency across design proposals by classifying Markdown files into categories like DESIGN and PROPOSAL, which generates tailored review criteria to assess document clarity and maintainability.

Automated document classification for technical guidelines and plans works by scanning Markdown files and categorizing them as GUIDELINE, PLAN, or other types, then generating targeted review criteria for each specific document type.

No, the documentation review process does not require specific external dependencies, allowing you to directly assess Markdown files and generate structured critiques without prior environment setup.

Automated criteria for issue specs ensure objective assessment of clarity and structure, generating consistent improvement recommendations across all ISSUE_SPEC documents without the variability of manual review.