verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: opzero1

Require verifiable evidence before marking tasks complete.

3|Updated Jan 15, 2026

Search Tags:#workflow #verification #completion #build #quality #evidence #tests

Ready to run

npx skills add https://github.com/opzero1/op1 --skill verification-before-completion-opzero1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/opzero1/op1/tree/main/packages/install/templates/skill/verification-before-completion
Command: npx skills add https://github.com/opzero1/op1 --skill verification-before-completion-opzero1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that any completion claim is backed by verifiable evidence, preventing done without proof.

Core Features & Use Cases

Enforces the requirement that completion claims include proof such as command outputs, test results, and build logs.
Integrates into project workflows to ensure verification before task closure.
Use Case: When finishing a feature, teams attach build success, test pass, and validation notes to prove it works.

Quick Start

Load this skill, trigger the verification checks before marking tasks complete, and attach the required evidence describing observed results.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I enforce verification before marking a task complete?▼

Requiring verification before completion ensures claims are backed by proof. You validate task closure by attaching command outputs, test results, and build success logs to demonstrate observable behavior and satisfy completion criteria.

What is verification before completion in software workflows?▼

Verification before completion is a workflow mechanism ensuring completion claims include verifiable proof. It prevents done without proof by enforcing requirements for command outputs, test results, and observable behavior before closing tasks.

How do I prevent developers from closing tasks without test results?▼

You prevent closing tasks without test results by integrating verification checks into project workflows. Enforce completion criteria requiring build success, command outputs, and validation notes as observable proof before allowing task closure.

Does verification before completion work with existing build and test workflows?▼

Verification before completion works with existing build and test workflows by integrating directly into them. It applies to code, builds, tests, and documentation workflows, enforcing command outputs and observable behavior before closure.

What counts as verifiable evidence for task completion?▼

Verifiable evidence for task completion includes command outputs, test results, build logs, and validation notes. These artifacts prove observable behavior and satisfy the completion criteria required before closing tasks.