Verification Before Completion

Name: Verification Before Completion
Availability: InStock
Author: slooowlly

Verify task completion with fresh test command output and build logs.

Updated Aug 27, 2026

Search Tags:#testing #quality assurance #code review #verification #completion #process

Ready to run

npx skills add https://github.com/Slooowlly/meu-modo-carreira-v4 --skill verification-before-completion-slooowlly

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Verification Before Completion
Source: https://github.com/Slooowlly/meu-modo-carreira-v4/tree/main/.agent/skills/verification-before-completion
Command: npx skills add https://github.com/Slooowlly/meu-modo-carreira-v4 --skill verification-before-completion-slooowlly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents dishonest or premature claims of task completion by enforcing a strict verification process before any success or completion is declared.

Core Features & Use Cases

Mandatory Verification: Ensures that all claims of success (tests passing, bugs fixed, builds succeeding, etc.) are backed by fresh, executed evidence.
Reduces Rework: Prevents shipping incomplete or broken work by catching issues before they are committed or merged.
Use Case: Before you tell your team lead that a feature is complete and ready for review, you must run the relevant test suite and confirm the output shows zero failures.

Quick Start

Before claiming any status or expressing satisfaction, identify the command that proves the claim, run it fresh, read the output, and verify it confirms the claim.

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 premature claims of task completion in software engineering?▼

To prevent premature claims of task completion, enforce a strict verification process mandating the execution and review of fresh evidence like test command output before any success is declared.

How do I verify code review success before declaring a task complete?▼

Verify code review success by identifying the command that proves your claim, running it fresh, reading the output, and confirming the evidence shows zero failures before declaring completion.

Why does my team face rework from incomplete or broken work being merged?▼

Rework from broken work happens when developers prioritize assumptions over evidence. Catching issues requires mandatory verification of test output and build logs before committing or merging code.

What is the best way to enforce quality assurance before claiming a bug is fixed?▼

The best way to enforce quality assurance before claiming a bug is fixed is to mandate the execution of relevant test suites and verify the output confirms zero failures prior to declaring success.

Does mandatory verification require any specific testing frameworks to work?▼

Mandatory verification does not require specific testing frameworks. It enforces a process of running and reviewing evidence like build logs or test commands to ensure work is genuinely correct.

When should I not use an evidence-based verification process for task completion?▼

An evidence-based verification process should not be bypassed when declaring any task completion, as skipping it risks dishonesty, trust issues, and shipping incomplete or broken work to your team.