Does it modify my original documentation files?

No, the skill performs a read-only review to maintain document integrity and outputs its findings into a separate markdown report.

How does it handle small projects versus large ones?

The skill uses proportional review logic, meaning it won't suggest enterprise-level patterns like microservices for a simple CLI tool or prototype.

Can it help identify over-engineering?

Yes, a core part of the workflow is dedicated to identifying unnecessary complexity, premature optimizations, and features that don't align with the project's current goals.

What types of documents can this skill review?

It is designed to review PRDs, specifications, implementation plans, technical designs, and any other documentation that defines software requirements or architecture.

Where are the review reports stored?

All reports are saved in the .agent_temp/reviews/ directory within your project root for easy reference and tracking.

Review Documentation & Specs

Name: Review Documentation & Specs
Author: tolo

bytolo

•

Learning & Documentation

Analyzes specifications, implementation plans, and PRDs to ensure technical accuracy, clarity, and readiness for development.

The review-doc skill enables Claude to act as a rigorous technical reviewer for software documentation, including PRDs, technical designs, and implementation plans. It systematically evaluates documents for completeness, identifies ambiguities, uncovers hidden edge cases, and flags potential over-engineering. By calibrating review depth to the project's specific scale—from MVPs to enterprise platforms—this skill ensures that your documentation is technically sound, pragmatic, and ready for immediate implementation without the risk of scope creep or architectural misalignment.

Key Features

01Automated report generation with prioritized findings and a readiness assessment.

021 GitHub stars

03Detection of over-engineering using KISS, YAGNI, and DRY principles.

04Proportional review logic that adjusts scrutiny based on project scale (MVP vs. Enterprise).

05Exhaustive edge case inventory covering security, network failures, and user journeys.

06Multi-phase analysis covering functional requirements, technical accuracy, and architecture.

Use Cases

01Validating a new PRD to ensure all functional requirements and success criteria are testable.

02Assessing a prototype plan to eliminate unnecessary complexity and premature optimizations.

03Reviewing a technical design document for architectural soundness and potential risks.

Key Features

01Automated report generation with prioritized findings and a readiness assessment.

021 GitHub stars

03Detection of over-engineering using KISS, YAGNI, and DRY principles.

04Proportional review logic that adjusts scrutiny based on project scale (MVP vs. Enterprise).

05Exhaustive edge case inventory covering security, network failures, and user journeys.

06Multi-phase analysis covering functional requirements, technical accuracy, and architecture.

Use Cases

01Validating a new PRD to ensure all functional requirements and success criteria are testable.

02Assessing a prototype plan to eliminate unnecessary complexity and premature optimizations.

03Reviewing a technical design document for architectural soundness and potential risks.