doc-review

Review documents for logic, strategy, technical feasibility, and risks.

2|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/ks6088ts-labs/skills --skill doc-review-ks6088ts-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-review
Source: https://github.com/ks6088ts-labs/skills/tree/main/skills/doc-review
Command: npx skills add https://github.com/ks6088ts-labs/skills --skill doc-review-ks6088ts-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring documents are clear, logical, strategically aligned, and technically sound, preventing costly errors and misinterpretations.

Core Features & Use Cases

  • Multi-faceted Review: Evaluates documents from strategic, logical, technical, risk, and clarity perspectives.
  • Actionable Feedback: Provides prioritized, constructive suggestions for improvement.
  • Use Case: Submit your product requirements document (PRD) to get a thorough review that identifies potential business risks, logical gaps, and areas needing technical clarification before development begins.

Quick Start

Review the attached document 'product_requirements.md' for clarity and strategic alignment.

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 product requirements document (PRD) for technical feasibility and strategic alignment?

To review a product requirements document for technical feasibility and strategic alignment, submit it to analyze logical structure, risk management, and expression accuracy using MECE and SMART frameworks, yielding prioritized constructive improvement suggestions.

What is document review using the 5W1H framework?

Document review using the 5W1H framework systematically evaluates proposals and technical specifications across business strategy, logical structure, technical feasibility, and risk management to identify logical gaps and provide constructive improvement suggestions.

How do I assess business risks and logical gaps in technical specifications?

Assess business risks and logical gaps in technical specifications by conducting a multi-faceted review that evaluates risk management and logical structure, identifying areas needing technical clarification to prevent costly errors before development begins.

Can I use SMART and MECE checklists to evaluate design documents?

Yes, you can use SMART and MECE checklists to evaluate design documents, analyzing them from multiple viewpoints including business strategy, technical feasibility, and expression accuracy to generate prioritized and actionable feedback.

What is the best way to get constructive feedback on a project proposal?

The best way to get constructive feedback on a project proposal is to conduct a comprehensive multi-faceted review, evaluating strategic alignment, logical structure, and technical soundness to prevent costly misinterpretations and yield prioritized suggestions.

When do I need a comprehensive document review for quality assurance?

You need a comprehensive document review for quality assurance when you must ensure proposals and technical specifications are clear, strategically aligned, and technically sound before development begins, preventing costly errors and misinterpretations.