reviewing-document-discovery

Reviews a produced document plan against a fourteen-condition bar and emits an 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-discovery-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-document-discovery
Source: https://github.com/bm629/agent-skills/tree/main/skills/reviewing-document-discovery
Command: npx skills add https://github.com/bm629/agent-skills --skill reviewing-document-discovery-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Before a project produces its documents, someone must independently judge whether the planned document set is sound — proportional to the project, complete, and producible. This Skill acts as that acceptance gate, preventing over-selected, under-selected, cyclic, or padded document plans from reaching production. ## Core Features & Use Cases - Fourteen-condition quality bar: Judges proportionality to the archetype, load-bearing documents, per-document production requirements, acyclic dependency graphs, orphan detection with a leaf-deliverable exception, padding, amend delta scoping, and manifest output-contract completeness. - Single terminal verdict: Emits exactly one machine-parseable VERDICT: approve or VERDICT: revise line plus actionable findings naming the affected documents and fixes. - Single-sourced with the authoring skill: Mirrors the Self-check of project-document-discovery 1:1 so the author and the independent gate enforce the same bar. - Use Case: After project-document-discovery produces a manifest for a new SaaS product, run this Skill to confirm the plan is right-sized, acyclic, and complete before any document is written. ## Quick Start Use reviewing-document-discovery on the produced document plan and the idea it was made for, then act on the verdict and findings.

Frequently Asked Questions about reviewing-document-discovery

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

FAQPage Schema
How do I review a document plan before producing documents?

Run this Skill on the produced document plan together with the idea and archetype it was made for. It judges fourteen conditions covering proportionality, dependencies, and manifest completeness, then emits one VERDICT: approve or revise line with actionable findings.

What is the difference between reviewing-document-discovery and reviewing-document-set?

reviewing-document-discovery is the up-front gate that judges whether a document plan is sound before anything is written. reviewing-document-set is the produced-corpus gate that checks whether finished documents are mutually coherent after they are written.

Does this Skill author or fix document plans?

No, it is strictly review-only. It reports findings naming the affected documents and how to fix them, and the producer skill such as project-document-discovery performs the actual revision.

Why does the reviewer flag a README or LICENSE as an orphan?

It should not. A leaf deliverable like LICENSE, CHANGELOG, or README with an empty depends_on and no downstream reader is a shippable end product, not an orphan, and flagging it is the most common false-revise this Skill is designed to avoid.

When should a lean document plan be approved?

A lean plan that is right-sized for a thin archetype, such as a README plus a short design note for a CLI tool, is an approve. Proportionality is judged against the archetype, never against a fixed taxonomy of documents.