skills.rest
arthrod
arthrodCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and analyze output before reporting task completion.

Updated Jul 18, 2026
Search Tags:#workflow#testing#tdd#quality assurance#verification#accountability
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill verification-before-completion-arthrod
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/arthrod/conejo-skills --skill verification-before-completion-arthrod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of shipping incomplete, broken, or unverified work by mandating that every claim of success be backed by fresh, objective evidence.

Core Features & Use Cases

  • Verification Gate: Forces a strict protocol of identifying, running, and reading verification commands before any status claim is made.
  • Rationalization Prevention: Provides a framework to identify and reject common excuses for skipping verification steps.
  • Use Case: Before marking a bug fix as complete, the agent must run the specific test case, confirm the failure is resolved, and document the output as proof.

Quick Start

Apply the verification-before-completion protocol to validate the current task status by running the necessary test suite and confirming the output before reporting success.

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

Enforce verification before completion by mandating a strict protocol to run specific test suites and analyze the output objectively before asserting any task success. This prevents shipping broken code by requiring fresh evidence for every status claim.

What is evidence-based work completion in software engineering workflows?▼

Evidence-based work completion is a quality assurance practice requiring objective proof, such as fresh test output, before validating any task status. It eliminates rationalization by forcing developers and agents to document verification commands and their results.

How do I stop agents from skipping test execution in delegated development tasks?▼

Stop agents from skipping tests by applying a verification gate that rejects common excuses. This framework requires agents to execute specific verification commands, confirm failures are resolved, and document the output before reporting task success.

Can I use verification protocols for pull request creation and bug fixes?▼

Yes, you can use verification protocols for pull request creation and bug fixes. Before marking a bug fix complete, the protocol requires running the specific test case, confirming the failure is resolved, and documenting the output as proof.

What is the best way to prevent shipping unverified code in automated pipelines?▼

The best way to prevent shipping unverified code is to implement a verification gate that identifies, runs, and reads verification commands before any success assertion. This ensures operational integrity by backing every claim with objective evidence.

Related Skills

Explore More Software Engineering Skills→
ksciuskscius
2

self-validate

Verify file existence, command availability, and test results before task completion.

Community
Advanced
hanibalskhanibalsk
3

verification-before-completion

Run verification commands and require evidence before completion claims.

Community
Basic
LerianStudioLerianStudio
205

dev-feedback-loop

Automate development-cycle metrics collection and generate improvement reports.

Official
Advanced
rsmdtrsmdt
381

specification-compliance

Validate implementations against documented specifications with structured compliance reporting.

Community
Advanced