audit-docs

Runs layered adversarial audits of specification documents using fresh reviewer agents.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/dxiiren/project-skeleton --skill audit-docs-dxiiren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-docs
Source: https://github.com/dxiiren/project-skeleton/tree/main/.claude/skills/audit-docs
Command: npx skills add https://github.com/dxiiren/project-skeleton --skill audit-docs-dxiiren

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Written specifications often contain contradictions, arithmetic errors, and gaps that only surface during a build. This Skill audits a document set with independent reviewer agents that never saw the author's reasoning, then verifies every claimed fix in the actual text before a build depends on the documents. ## Core Features & Use Cases - Layered adversarial audits: A cross-set consistency pass, a mandatory re-verify round after fixes, a targeted confirmation round, and per-document deep dives with document-specific lenses. - Provable findings and verdicts: Every finding cites a file and section with a prescribed fix, classified as BLOCKER, MAJOR, or MINOR, and rolled up into CLEAN, PASS-WITH-FIXES, or FIX-FIRST verdicts. - Audit trail recording: Writes dated audit logs to audits/ with reconciled counts, per-round verdicts, and honest caveats about what was not verified. - Use Case: Before building from a requirements pipeline (BRD, PRD, FSD, TDD), run the audit to catch cross-document contradictions, recompute formulas, and confirm the fix pass did not introduce new defects. ## Quick Start Ask the AI to audit the docs in your specification folder before starting the build.

Frequently Asked Questions about audit-docs

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

FAQPage Schema
How do I audit a requirements specification before building from it?

Run the audit-docs skill on the document set. It dispatches a fresh agent to read every document for cross-file contradictions, traceability gaps, and arithmetic errors, then applies fixes and re-verifies them in the text before issuing a verdict.

How to review documents with independent AI agents?

Dispatch read-only auditor agents that receive only the documents, domain context, and what earlier rounds fixed, never the author's reasoning. Give each an explicit model setting and a structured output format of severity-tagged findings.

Why re-audit documents after applying fixes?

Fix passes reliably introduce new defects, such as fresh contradictions at the seams they touched. A mandatory re-verify round confirms each finding is resolved in the actual text and hunts for regressions the fixes created.

What documents can this audit process check?

It handles any document set a build depends on: discovery notes, BRDs, PRDs, functional and technical design specs, index trackers, research appendices, and even the audit log itself, each with a document-specific review lens.

When should I not trust a clean audit verdict?

Distrust a clean verdict when a layer was skipped without disclosure, when resolutions were accepted from a log without opening the files, or when the count chain does not reconcile with the listed findings. The skill requires reporting what was not verified.