build-reviewerlisted

Conducts final production-readiness review of any governed document pack — Copilot Builder Agent, PMO platform, security, or generic — using the shared review discipline. Domain dimensions load from pluggable packs under `references/dimension-packs/` (4 packs: copilot-builder, pmo-platform, security, generic); the security pack carries AppSec/SecOps dimensions. Produces a structured findings register (severity · root cause · evidence · resolution · reversibility) per finding, consumed by implementation-planner downstream. Use when the user wants a final production-readiness review of a document pack or platform surface, including: "review the copilot builder files", "audit the pmo platform", "review this document pack", "find gaps in the builder doc pack", "run the security dimension pack", "run the vulnerability assessment", "triage these dependency CVEs", "which of these CVEs are actually reachable", "secure-coding and secret-exposure review", "triage the penetration-test findings".
cody-hutson/pmo-platform · ★ 0 · AI & Automation · score 62

Install: claude install-skill cody-hutson/pmo-platform

> **See also:** > - [`core/disciplines/review-discipline-principles.md`](../../../core/disciplines/review-discipline-principles.md) — shared review discipline (anti-laziness rules, root-cause requirement, 6-deliverable output structure, reviewer calibration, anti-patterns for reviewers). > - [`references/dimension-packs/README.md`](references/dimension-packs/README.md) — dimension-pack registry and domain-detection rules. > - [`core/standards/failure-mode-standard.md`](../../../core/standards/failure-mode-standard.md) — failure-mode format (governs `## Domain-Specific Failure Modes` section below). > - [`core/specs/reversibility-protocol.md`](../../../core/specs/reversibility-protocol.md) — reversibility tier vocabulary (governs Reversibility Discipline section below). > - [`core/standards/domain-best-practices/software.md`](../../../core/standards/domain-best-practices/software.md) § Security — the four codified control-hygiene concepts (fail-closed controls, input validation, sink-context output encoding, injection resistance) the `security` pack's Area A **operationalizes** into review dimensions, one dimension per concept (SEC-D1–D4). This is a deliberate operationalization, not a bare pointer: Area A's what-to-check bullets render the guide's Design-consumption notes in check form, so the two surfaces share phrasing by construction. The guide stays the **single authoritative source of the rule**; the pack is its **review-time re