review-document

Review prose documents for correctness, consistency, clarity, and claim accuracy.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/AndreJorgeLopes/devflow --skill review-document
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-document
Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/review-document
Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill review-document

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires defuddle, and includes references (resource) components.

What problem does it solve?

Review-document prevents slow, error-prone document reviews by automatically checking prose documents for correctness, internal consistency, completeness, clarity, and external-claim accuracy.

Core Features & Use Cases

  • Multi-perspective review: Runs dedicated role-based agents (critic, writer, and—when relevant—verifier, architect, security, and external document specialist) to cover substance, readability, and claim risk.
  • Platform-aware fetching: Accepts Google Docs, Confluence pages, local files, or URLs, then fetches clean text to avoid track-changes/suggestion artifacts.
  • Context-aware deduping: Cross-checks against existing platform comments to avoid re-flagging the same issues, and returns severity-tagged findings anchored to the doc.
  • Quick or thorough modes: Uses quick for a single-pass sanity review and thorough for deeper, multi-agent analysis.

Quick Start

Ask the AI to run review-document on your PRD in Google Docs thorough mode so it returns severity-tagged, anchored fixes.

Frequently Asked Questions about review-document

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

FAQPage Schema
How do I review a PRD for internal consistency and external claim accuracy?

You can review a PRD by running a multi-agent prose audit that checks correctness, internal consistency, clarity, and external-claim accuracy, returning severity-tagged findings anchored to the document.

Can I review documents hosted on Google Docs or Confluence?

Yes, you can review documents hosted on Google Docs or Confluence. The platform-aware fetching mechanism accepts Google Docs, Confluence pages, local files, or arbitrary URLs, fetching clean text to avoid track-changes or suggestion artifacts during the document review.

What is the difference between quick and thorough modes for document review?

The difference between quick and thorough modes is that quick performs a single-pass sanity review, while thorough executes a deeper, multi-agent analysis using dedicated role-based agents like critic, writer, verifier, and security to cover substance, readability, and claim risk.

How do I prevent duplicate comments when running a prose audit on a knowledge base?

To prevent duplicate comments during a prose audit, the review process cross-checks against existing platform comments already present in the document, ensuring context-aware deduping so it avoids re-flagging the same issues previously identified.

Does document review work with local files and arbitrary URLs?

Yes, document review works with local files and arbitrary URLs. It applies to knowledge base articles, RFCs, spikes, runbooks, PRDs, and design docs by fetching clean text from local files, Google Docs, Confluence pages, or arbitrary URLs.

When should I use a multi-agent check for a design doc?

You should use a multi-agent check for a design doc when you need to prevent slow, error-prone reviews by automatically verifying substance, readability, and external-claim risk through dedicated role-based agents like architect, security, and verifier.