completeness-gate

Compare deliverables against spec success criteria and report PASS or FAIL with evidence.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill completeness-gate-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: completeness-gate
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/completeness-gate
Command: npx skills add https://github.com/michael-conrad/.opencode --skill completeness-gate-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Completeness-gate verifies that a deliverable is present, structurally sound, and fully covers the spec's success criteria before routing to the auditor.

Core Features & Use Cases

  • Read-only gate that inspects deliverables against spec criteria.
  • Enforces mandatory steps via sub-agent orchestration, and preserves evidence for auditing.
  • Use cases include post-RED/GREEN handoffs, readiness checks for audit pipelines, and early validation of spec coverage before auditor routing.

Quick Start

Provide the spec and deliverable artifacts to the gate, then trigger the completeness check to validate coverage and readiness for audit.

Frequently Asked Questions about completeness-gate

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

FAQPage Schema
What is a completeness gate in an audit pipeline?

A completeness gate is a read-only verification step that compares deliverables against spec success criteria to identify gaps and report PASS or FAIL with evidence before auditor routing.

How do I verify deliverable readiness before routing to an auditor?

To verify deliverable readiness, provide the spec and deliverable artifacts to the completeness gate to validate structural soundness and full coverage of success criteria before audit routing.

When should I run a completeness check after RED/GREEN sub-agent results?

You should run a completeness check immediately after RED/GREEN sub-agent results and before auditor routing to ensure the deliverable fully covers the spec's success criteria.

Does the completeness gate modify deliverables or provide remediation advice?

No, the completeness gate operates as a read-only procedure with strict result contracts, meaning it only collects evidence and reports PASS or FAIL without performing remediation or routing advice.

What is the best way to enforce mandatory evidence collection during spec verification?

The best way to enforce mandatory evidence collection is using a completeness gate that mandates task dispatching and evidence collection via sub-agent orchestration to preserve verification artifacts for auditing.