verification-before-completion

Run validation commands and review output logs before claiming task completion.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/edlng/agents --skill verification-before-completion-edlng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/edlng/agents/tree/main/skills/universal/verification-before-completion
Command: npx skills add https://github.com/edlng/agents --skill verification-before-completion-edlng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of claiming work is complete or successful without actual evidence, ensuring high-quality output and maintaining trust between the agent and the user.

Core Features & Use Cases

  • Verification Gate: Mandates a strict protocol of identifying, running, and verifying commands before any status claims are made.
  • Rationalization Prevention: Provides a framework to identify and reject common excuses for skipping verification steps.
  • Use Case: Before finalizing a bug fix, the agent must run the specific test case that failed, confirm the output shows zero failures, and only then report the bug as resolved.

Quick Start

Apply the verification before completion protocol to the current task by identifying the specific command that proves success and executing it before making any final claims.

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 software task is complete?

Enforce verification before task completion by mandating a strict protocol to identify, execute, and validate specific commands with objective evidence before any success claims are made.

Why do automated agents claim work is finished without actual evidence?

Agents claim work is finished without evidence due to rationalization and skipping validation steps. This behavior is prevented by a framework that rejects common excuses and requires objective proof of state changes.

What is the best way to validate a bug fix before reporting it as resolved?

Validate a bug fix by running the specific failed test case, reviewing the full output logs to confirm zero failures, and only then reporting the bug as resolved to ensure accuracy and reliability.

Does this verification protocol require specific testing dependencies to run?

No specific testing dependencies are required. The verification protocol applies generically to software development and agentic workflows by executing existing validation commands and reviewing their output logs.

How do I stop my workflow from skipping quality assurance steps during task completion?

Stop skipping quality assurance steps by applying a verification gate that mandates the execution of specific validation commands and the review of full output logs before any status claims are made.

When do I need to apply a validation gate in an agentic software workflow?

Apply a validation gate in agentic software workflows whenever objective evidence is required before asserting success, such as finalizing bug fixes, testing, or completing development tasks.