verification-before-completion

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

Run verification commands and evaluate fresh output before claiming completion.

Updated Jan 31, 2026

Search Tags:#workflow #verification #completion #governance #evidence #quality-assurance #claims

Ready to run

npx skills add https://github.com/involvex/image-wizard-cli --skill verification-before-completion-involvex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/involvex/image-wizard-cli/tree/main/.gemini/skills/verification-before-completion
Command: npx skills add https://github.com/involvex/image-wizard-cli --skill verification-before-completion-involvex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonesty, not efficiency. This guidance enforces a disciplined approach where completion can only be claimed after fresh verification evidence has been produced.

Core Features & Use Cases

Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.
The Gate Function: Before claiming status, identify the verification command to run, execute it fully, read the output, verify against success criteria, and only then declare completion.
Common Failures: Highlights typical mistakes such as relying on outdated results, skipping full command runs, or asserting success without objective evidence.
Use Case: Teams validating release readiness, code reviews, or task closures in CI/CD or project-management workflows require fresh verification before reporting completion.

Quick Start

Run the verification workflow and only claim completion after confirming fresh evidence.

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 claiming a task is complete?▼

To enforce verification before claiming completion, you must run the relevant verification commands, evaluate the fresh output against success criteria, and document the results as evidence before asserting any work is done.

Why does reporting completion without fresh evidence cause workflow failures?▼

Reporting completion without fresh verification evidence causes workflow failures because it relies on outdated results or assumptions, skipping the objective validation needed to confirm outcomes in quality-assurance and release-readiness workflows.

What is the best way to prevent premature completion claims in CI/CD pipelines?▼

The best way to prevent premature completion claims in CI/CD pipelines is to implement a gate function that executes verification commands fully and validates fresh output before any completion status is reported.

How do I document evidence when asserting task completion in project management?▼

To document evidence when asserting task completion, run the required verification commands, capture the fresh output, verify it meets your success criteria, and provide that documented evidence alongside your completion claim.

Can I use previous test results to verify code review readiness?▼

No, you cannot use previous test results to verify code review readiness. You must execute verification commands to produce fresh output and evaluate it against success criteria before declaring any task complete.

What are common failures when verifying outcomes before reporting success?▼

Common failures when verifying outcomes include relying on outdated results, skipping full verification command runs, and asserting success without producing or evaluating objective fresh evidence against defined criteria.