verification-before-completion

Run verification commands and review outputs before declaring work complete.

Updated Dec 11, 2024
One-click install
npx skills add https://github.com/huaxel/dotfiles --skill verification-before-completion-huaxel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/huaxel/dotfiles/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/huaxel/dotfiles --skill verification-before-completion-huaxel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification can lead to misinformation and low-quality outcomes. This skill enforces a disciplined process where fresh verification evidence is required before declaring work complete.

Core Features & Use Cases

  • Enforces verification before completion claims, including running specified verification steps and reviewing outputs.
  • Standardizes evidence collection, exit status checks, and report-ready status updates.
  • Use Case: In AI-assisted tasks, require a verification pass before delivering results to a stakeholder to prevent premature claims.

Quick Start

Run the verification command, read the full output, and only claim completion when the results show verifiable success with 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 prevent false completion claims in AI-assisted tasks?

Prevent premature completion claims in AI-assisted tasks by enforcing verification steps before delivering results to stakeholders. Run fresh verification commands, review the full outputs, and only report completion when verifiable evidence of success is confirmed.

What is verification before completion in software development?

Verification before completion is a governance process that standardizes evidence collection and exit status checks to prevent misinformation. It requires running fresh verification commands and reviewing their full outputs before reporting a verifiable success status.

How do I enforce evidence collection before reporting task completion?

Enforce evidence collection before reporting task completion by standardizing the process of running verification commands and checking exit statuses. You must review the full command outputs and prepare a status update only after confirming verifiable evidence of the results.

Does this verification process work for QA checks and software workflows?

Yes, this verification process works for QA checks and software workflows by applying a standardized governance approach. It requires running fresh verification commands, reviewing outputs, and confirming verifiable evidence before declaring any task or workflow complete.

What are the limitations of declaring work done without verification?

Declaring work done without verification leads to misinformation and low-quality outcomes due to unverified claims. Without running fresh verification commands and reviewing evidence, you risk reporting false completion statuses and delivering premature claims to stakeholders.