reviewing-document-set

Reviews a set of project documents for cross-document coherence and emits one approve or revise verdict.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill reviewing-document-set-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-document-set
Source: https://github.com/bm629/agent-skills/tree/main/skills/reviewing-document-set
Command: npx skills add https://github.com/bm629/agent-skills --skill reviewing-document-set-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Individually well-written project documents can still contradict each other, drop requirements, or drift out of sync, and no single-document review catches that. This Skill judges a finished set of documents as one corpus to decide whether they are mutually coherent and ready to plan from. ## Core Features & Use Cases - Eight-dimension coherence bar: Checks cross-document consistency, root-anchored traceability, contradictions, dependency integrity, divergent duplication, ready-to-plan sufficiency, amend re-review, and version skew. - Single machine-parseable verdict: Emits exactly one terminal VERDICT: approve|revise line, with every finding prefixed by the affected document ids so fixes can be routed per document. - Delta-scoped re-review: When one document changes, it traces the ripple only to dependent documents instead of re-auditing the whole corpus. - Use Case: After a PRD, architecture doc, and API spec each pass their own reviews, run this Skill on the set to confirm the API spec still matches the PRD's auth model before planning begins. ## Quick Start Use reviewing-document-set on my PRD, architecture doc, and API spec to check they are mutually coherent and ready to plan from.

Frequently Asked Questions about reviewing-document-set

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

FAQPage Schema
How do I review multiple project documents for consistency?

Hand the full set of finished documents to the reviewer and it applies an eight-dimension cross-document checklist covering consistency, traceability, contradictions, and dependency integrity. It returns findings attributed to specific document ids plus one approve or revise verdict.

What is the difference between reviewing one document and reviewing a document set?

A single-document review judges one document's internal quality, while a document-set review judges only how documents relate to each other. This Skill assumes each document already passed its own gate and never re-litigates internal quality.

How do I re-review documents after one of them changed?

Hand in the set with the stated change or delta, and the amend re-review dimension traces the ripple only to documents that declare the changed doc as an upstream. It re-validates just the affected edges rather than the whole corpus.

When should I not use a corpus-level document review?

Do not use it for a single document, since there are no cross-document relationships to judge, and do not use it to author or fix documents. It is review-only and reports findings for the producers to act on.

Why does a document set review approve a small set with missing dimensions?

The audit scales with corpus size, so amend re-review is not applicable on a greenfield first-pass and version-skew is not applicable on a single-version set. Applying a heavyweight audit to a thin corpus would produce false revise verdicts.