verification-before-completion

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

Enforce fresh verification evidence before declaring task completion.

Updated Mar 8, 2026

Search Tags:#automation #verification #evidence #gates #quality-assurance #code-review #plan-driven

Ready to run

npx skills add https://github.com/ReadyStateChange/agents --skill verification-before-completion-readystatechange

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ReadyStateChange/agents/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/ReadyStateChange/agents --skill verification-before-completion-readystatechange

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature completion claims by requiring fresh verification evidence before you state success.

Core Features & Use Cases

Enforces running fresh verification commands before declaring success.
Provides a repeatable gate (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) to ensure evidence-backed results.
Integrates with plan-driven workflows to confirm plan criteria before updates.

Quick Start

Identify the verification command for your task, run it now, and report the fresh results to confirm completion.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I prevent premature completion claims in software development?▼

Require fresh verification evidence before declaring success to prevent premature completion claims. Use a repeatable gate (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) to enforce running verification commands and reporting evidence-backed results.

What is the verification gate process for code review and QA workflows?▼

The verification gate process enforces a five-step sequence: IDENTIFY the verification command, RUN it, READ the output, VERIFY the results, and ONLY THEN declare success. This ensures evidence-backed completion in code review and QA workflows.

How do I enforce evidence-backed results in plan-driven workflows?▼

Enforce evidence-backed results in plan-driven workflows by applying the verification gate before updating task status. You must identify the relevant verification command, run it, and confirm the output matches plan criteria before stating completion.

Does this verification approach work with existing quality assurance automation?▼

Yes, this verification approach integrates with existing quality assurance automation by enforcing the execution and reporting of fresh verification commands. It acts as a gate to confirm automation results before any success is declared.

When should I require fresh verification evidence before declaring success?▼

You should require fresh verification evidence whenever a software development, code review, or QA task is ready to be marked complete. This prevents declaring success based on assumptions rather than verifiable, freshly generated results.