doc-review

Review specification documents against completeness, clarity, consistency, and implementability criteria.

Updated Aug 27, 2026

Search Tags:#quality assurance #feedback #documentation #specification #product management #review

Ready to run

npx skills add https://github.com/nishio-n0522/test_updated_sdd --skill doc-review-nishio-n0522

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-review
Source: https://github.com/nishio-n0522/test_updated_sdd/tree/main/.claude/skills/doc-review
Command: npx skills add https://github.com/nishio-n0522/test_updated_sdd --skill doc-review-nishio-n0522

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured methodology and clear criteria for reviewing various specification documents, ensuring clarity, completeness, and implementability.

Core Features & Use Cases

Comprehensive Review Checklist: Covers completeness, clarity, consistency, implementability, and measurability.
Document-Specific Criteria: Tailored checks for PRDs, functional specs, UI specs, and more.
Severity Classification: Categorizes feedback into MUST, SHOULD, and MAY for prioritized action.
Use Case: A product manager can use this Skill to ensure a newly drafted PRD is ready for engineering by having the AI review it against all defined criteria and provide actionable feedback.

Quick Start

Review the attached 'product-requirements.md' document using the doc-review skill.

Frequently Asked Questions about doc-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review a PRD for engineering readiness?▼

Reviewing a PRD involves checking it against completeness, clarity, consistency, implementability, and measurability criteria to ensure it is fully prepared for engineering teams to implement.

What is the best way to provide structured feedback on specification documents?▼

Providing structured feedback on specification documents is best achieved by categorizing review comments into MUST, SHOULD, and MAY severity classifications to prioritize actionable engineering tasks.

When do I need to use a formal methodology to review functional design documents?▼

You need a formal review methodology for functional design documents when you must verify implementability and consistency across complex product features before handing them to engineering.

Can I use a standardized review checklist for UI specifications?▼

Yes, you can use a standardized review checklist for UI specifications to systematically measure clarity, consistency, and completeness, ensuring all interface requirements are clearly defined for implementation.

What criteria should a product manager use to check a specification document?▼

A product manager should check a specification document using criteria that cover completeness, clarity, consistency, implementability, and measurability to guarantee the product requirements are actionable.