critical-document-reviewer

Detect unsupported claims, logical gaps, and risks in design and requirements documents.

5|4|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/takusaotome/claude-skills-library --skill critical-document-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critical-document-reviewer
Source: https://github.com/takusaotome/claude-skills-library/tree/main/skills/critical-document-reviewer
Command: npx skills add https://github.com/takusaotome/claude-skills-library --skill critical-document-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you catch hidden weaknesses in high-stakes documents by verifying claims, evidence, logic, security, testability, and operational readiness from multiple expert personas.

Core Features & Use Cases

It runs a multi-persona critical review (Developer, PM, Customer, QA, Security, Ops) in parallel to detect ambiguity, unsupported statements, logical gaps, weak traceability, confirmation bias, test-infeasible requirements, security risks, and operational concerns. It also supports larger documents by switching to a scale strategy that prioritizes high-impact sections before checking the rest.

Quick Start

Ask it to critically review your design/requirements/incident/proposal document and produce a structured critical review report with prioritized issues and recommended actions.

Frequently Asked Questions about critical-document-reviewer

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

FAQPage Schema
How do I detect unsupported claims and logical gaps in a requirements document?

A multi-persona critical review validates requirements documents by verifying evidence, logic, and traceability from Developer, PM, Customer, QA, Security, and Ops perspectives to detect unsupported claims and logical gaps.

What is the best way to check operational readiness and security risks in a design document?

Checking operational readiness and security risks in a design document is best handled by applying a multi-persona critical review that evaluates evidence and flags testability or operational concerns before execution.

How do you validate incident reports for missing traceability and confirmation bias?

You validate incident reports for missing traceability and confirmation bias by applying evidence-based scrutiny across multiple expert personas to detect ambiguity and verify claims.

Can I review large proposal documents for testability risks without losing context?

Yes, you can review large proposal documents for testability risks by switching to a scale strategy that prioritizes high-impact sections before checking the rest, ensuring context is maintained.

Does multi-persona critical review work for checking document quality before acceptance?

Yes, multi-persona critical review works for checking document quality before acceptance by producing a structured report with prioritized issues and integrated severity classification.

When should I not use automated evidence validation for requirements QA?

Automated evidence validation for requirements QA should not be used when you lack dedicated reference frameworks for evidence evaluation and red-flag detection, as it relies on structured multi-persona analysis.