verification-before-completion

Verify work completion with evidence before making success claims.

Updated Oct 25, 2023

Search Tags:#testing #quality assurance #code review #verification #honesty #process enforcement

Ready to run

npx skills add https://github.com/Lordkaito/LKPortfolio --skill verification-before-completion-lordkaito

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the premature declaration of work completion or success by enforcing a strict verification process before any claims are made. It combats dishonesty and inefficiency stemming from unverified assertions.

Core Features & Use Cases

Mandatory Verification: Ensures that all claims of completion, passing tests, or bug fixes are backed by fresh, verifiable evidence.
Structured Verification Process: Provides a clear, step-by-step "Gate Function" to follow before making any success claims.
Use Case: Before committing code, an engineer must run the relevant test suite, verify the output shows zero failures, and then state "All tests pass with 0 failures" along with the command used.

Quick Start

Always run the verification command and read its output before claiming any status or expressing satisfaction.

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 a verification process before claiming code review tasks are complete?▼

To prevent premature success claims, mandate a strict verification protocol requiring fresh evidence before any assertions are made. This Gate Function forces engineers to run test suites and verify zero failures before declaring work completion, maintaining honesty and process enforcement.

What is a Gate Function for quality assurance and how does it work?▼

A Gate Function for quality assurance is a structured protocol blocking success assertions until verifiable evidence is produced. It requires running relevant commands, reading the output to confirm zero failures, and then stating the result with the command used before declaring completion.

Why does my testing workflow allow premature declarations of success?▼

Your testing workflow allows premature declarations because it lacks a mandatory verification step. Without enforcing an Iron Law requiring evidence to precede assertions, engineers claim bugs are fixed without running the test suite to generate fresh, verifiable output confirming zero failures.

How do I verify bug fixes before committing code?▼

To verify bug fixes before committing code, run the relevant test suite and read the output to ensure zero failures. Then state the result, such as "All tests pass with 0 failures," along with the command used, adhering to strict process enforcement and honesty protocols.

Does this verification process work for all stages of software development?▼

Yes, this verification process applies to all stages of software development and task completion. It enforces a universal protocol requiring evidence before any declaration of success, ensuring honesty and preventing unverified assertions across the entire development lifecycle.

What are the limitations of relying on assertions without running test suites?▼

Relying on assertions without running test suites leads to dishonesty and inefficiency from unverified claims. Without executing commands to generate fresh output, you cannot guarantee zero failures, risking premature success declarations and compromised quality assurance.