verification-before-completion

Require fresh verification output before declaring task completion or success.

5|Updated Feb 6, 2026

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

Ready to run

npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill verification-before-completion-faisalalqarni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/FaisalAlqarni/sp-ecc/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/FaisalAlqarni/sp-ecc --skill verification-before-completion-faisalalqarni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of task completion, bug fixes, or passing tests by enforcing a strict verification process before any assertion of success is made.

Core Features & Use Cases

Mandatory Verification: Ensures that evidence (command output, test results) is gathered before declaring a task complete, a bug fixed, or tests passing.
Reduces Rework: Prevents shipping incomplete or broken code by catching issues early through rigorous, fresh verification.
Use Case: Before committing code that is supposed to fix a bug, you must run the relevant test command, confirm it passes, and then present that output as evidence of the fix.

Quick Start

Always run the verification command and check its output before stating that work is complete.

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 evidence before claiming task completion in code review?▼

To enforce evidence before claiming task completion, you must run relevant test commands and capture their output before declaring a bug fixed or a task complete. This verification process prevents premature assertions of success in your development workflow.

What is the best way to prevent premature declarations of success during quality assurance?▼

The best way to prevent premature declarations of success is to implement a strict evidence before assertions policy. This requires gathering fresh verification output, such as test results, before making any claims of correctness or completion in your status reporting.

How do I verify a bug fix before committing code changes?▼

To verify a bug fix before committing, run the relevant test command, confirm it passes, and present that output as evidence of the fix. This rigorous quality assurance step catches incomplete code early and reduces rework.

Do I need to run test commands before reporting that tests are passing?▼

Yes, you need to run test commands and check their output before reporting that tests are passing. Mandatory verification ensures you gather fresh command output as evidence, preventing inaccurate status updates and building trust in the development workflow.

When do I need to apply a verification policy for task completion?▼

You need to apply a verification policy for task completion whenever you claim success, correctness, or completion of work. This applies to all status reporting, bug fixes, and code reviews to ensure rigorous quality assurance and prevent shipping broken code.