← ClaudeAtlas

agent-acceptance-gatelisted

Use when reconciled multi-agent output needs an evidence-based PASS, CONDITIONAL PASS, or FAIL record before authorized delivery.
WenyuChiou/agent-collab-skills · ★ 26 · AI & Automation · score 80
Install: claude install-skill WenyuChiou/agent-collab-skills
# agent-acceptance-gate Run the final read-only verification step for a multi-agent round. The gate checks declared criteria and produces acceptance evidence. It never merges, commits, retries, or silently converts a decline, cancellation, timeout, or failure into success. ## Inputs - current provider-neutral plan and success criteria; - validated `TaskCheckpoint` and latest `PolicyDecision`; - task results, evidence references, and raw-log paths; - reconciliation report; - repository diff and project-specific verification commands; - prior human decision records, if any. Historical provider fields may be read for migration only. Current checks use task IDs and roles (`primary-agent`, `delegated-executor`, `reviewer`, and `synthesizer`). ## Mandatory preset routing Run the matching preset when a staged diff: - touches multiple locale variants of the same document stem; - adds entries to a catalog; or - changes a model-and-benchmark claim. The bundled preset names are `multi-locale-mirror-sync`, `catalog-entry-add`, and `fact-check-frontier-models`. Presets encode additional failure-mode checks; they do not replace independent review or factual source verification. If a preset cannot run, report a blocker or explicit degraded state. Never claim PASS. ## Workflow 1. Validate the plan, checkpoint, and policy. Unreadable configured policy is a fail-closed blocker. 2. Inventory all tasks and required artifacts. Missing, `null`, declined, cancelled, timeout, degrad