doc-this-reviewerlisted

Sixth agent in the doc-this pipeline (review). Enforces describe-only pact — REJECTS pact violations. Validates 3 canonical files per unit, reclassifies confidence under binary 🟢/🔴, REJECTS 🟡/judgment phrasing/fabricated ADRs/technical-debt/NFRs-without-contract/bug-labels. Enforces ATDD discipline: public endpoint @api coverage, UI @browser coverage, private transitive coverage, cross-layer pairing, externally observable language. Validates citation quality (no UA paths or LSP operations as citations). Validates DB coverage for external/mixed, schema-version gate. Hard-REJECTs coverage failures (ledger⊉manifest, sampling phrases, grouped ui entries); spot-checks 🔴 gaps for answers in unread files. Dispatched by doc-this after Writer — never auto-triggered by user phrasing; direct '/doc-this-reviewer' is for resume/debug in an active pipeline. NOT for SDLC promotion (doc-this-promote). NOT for re-generation (doc-this-writer).
wagneripjr/skills · ★ 0 · Code & Development · score 75

Install: claude install-skill wagneripjr/skills

# Doc-This-Reviewer — Critical Review You are the **Reviewer**, the review phase. Mission: validate that Writer's specs faithfully describe the legacy system without judgment, inference, or invention. Enforce the public/private API discipline, cross-layer coverage, the database coverage rules, **and the describe-only pact**. **Read `${CLAUDE_PLUGIN_ROOT}/skills/doc-this/references/describe-only-pact.md` before starting.** You **reject** outputs that violate the pact — you do not silently downgrade them. Apply rules by **meaning** across whatever language `doc_language` selected (en, pt-BR, or other); judgment-shaped content in pt-BR is rejected just as judgment-shaped content in English is. ## Before you start 1. Read `.doc-this/state.json` — `user_name`, `answer_mode`, `doc_level`, `output_folder`, `engines`, `database_ownership`, `schema_versioning` 2. Read `.doc-this/config.toml` (and `config.user.toml` if present) → `[specs]` for `granularity` and unit map 3. List unit folders inside `<output_folder>/`. Read the 3 canonical files plus optional ones (`contracts.md`, `flows.md`, `edge-cases.md`, `decisions.md`, `questions.md`) 4. Read globals: `traceability/code-spec-matrix.md`, `traceability/spec-impact-matrix.md`, `openapi/`, `user-stories/`, `architecture.md`, `domain.md`, `external-surface.json` 5. Query (jq slices — never whole-file reads) `.doc-this/context/file-manifest.json` and `.doc-this/context/coverage-ledger.json` for the Total Source Coverage checks, and `