verification-before-completion

Enforce pre-completion verification gates requiring reproducible evidence before PRs or deployments.

121|29|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/KbWen/agentic-os --skill verification-before-completion-kbwen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/KbWen/agentic-os/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/KbWen/agentic-os --skill verification-before-completion-kbwen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Any "completed" statement MUST be supported by evidence. This skill provides a pre-completion Gate Function, ensuring results are reproducible, traceable, and deliverable.

Core Features & Use Cases

  • Guardrails and gate-driven verification ensure that completion is only declared when reproducible evidence exists.
  • Enforces a multi-gate workflow (Scope, Quality, Evidence, Risk, Communication) to validate work before ship or handoff.
  • Real-world use: before opening a PR or shipping code, require explicit, reproducible evidence of tests and validations.

Quick Start

Provide a completion claim only after compiling reproducible evidence and running the required gates.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I require verifiable evidence before declaring a software task complete?

To require verifiable evidence before completion, you enforce a pre-completion gate function that validates reproducible test results and traceability before any PR or deployment is approved.

What is a pre-completion verification gate in software development workflows?

A pre-completion verification gate is a checkpoint mechanism ensuring completion claims are backed by reproducible evidence, enabling safe handoffs and traceability across development cycles.

How do I enforce quality checks and traceability before opening a PR?

You enforce quality checks before opening a PR by running a multi-gate sequence covering Scope, Quality, Evidence, Risk, and Communication to validate work and compile reproducible evidence.

Can I use a multi-gate workflow to validate deployments and ship code safely?

Yes, you can use a multi-gate workflow to validate deployments by requiring explicit, reproducible evidence of tests across Scope, Quality, Evidence, Risk, and Communication gates before shipping code.

What's the best way to guarantee reproducibility and traceability during software handoffs?

The best way to guarantee reproducibility during handoffs is enforcing gate-driven verification that requires explicit evidence of validations before any completion statement is accepted.

When do I need gate-driven verification for completion claims?

You need gate-driven verification for completion claims whenever development cycles require safe handoffs, ensuring that PRs, ships, and deployments are gated by reproducible evidence.