verification-before-completion

Require command-based verification evidence before reporting task completion.

Updated Nov 18, 2025

Search Tags:#workflow #testing #quality assurance #best practices #verification #accountability

Ready to run

npx skills add https://github.com/conejoRojo/DeployTime --skill verification-before-completion-conejorojo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/conejoRojo/DeployTime/tree/main/_agent/skills/verification-before-completion
Command: npx skills add https://github.com/conejoRojo/DeployTime --skill verification-before-completion-conejorojo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of claiming work is finished or successful without actual proof, ensuring that all assertions are backed by verifiable evidence.

Core Features & Use Cases

Verification Gate: Mandates the execution of specific commands to prove success before any claim is made.
Rationalization Prevention: Provides a framework to identify and stop common excuses for skipping verification steps.
Use Case: Before submitting a pull request, use this skill to ensure that all regression tests have been run and that the output explicitly confirms zero failures.

Quick Start

Run the verification before completion skill to validate the current state of the project by executing the necessary test suite commands.

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 task completion in software development?▼

Run your full test suite commands and independently confirm the output explicitly shows zero failures before submitting a pull request. This enforces a strict verification protocol requiring fresh, command-based evidence for all task completion claims.

What is evidence-based work completion in testing workflows?▼

Evidence-based work completion prevents claiming work is finished without actual proof by mandating the execution of specific verification commands. It requires independent confirmation of command output before any success status is communicated.

Why does my agent claim work is successful without running verification?▼

Agents often rationalize skipping verification steps due to common excuses. A verification gate provides a framework to identify and stop these rationalizations, mandating full command execution before completion can be claimed.

Can I use this verification protocol for agent-based task delegation?▼

Yes, this verification protocol applies to agent-based task delegation alongside software development workflows and pull request submissions. It requires delegated agents to execute full verification commands and provide independent confirmation of output.

What's the best way to stop rationalizing skipped verification steps?▼

The best way to stop rationalizing skipped verification is implementing a framework that identifies common excuses and enforces a strict verification gate. This requires running full verification commands and confirming output independently before status updates.