verification-before-completion

Require fresh verification evidence before claiming software task completion.

Updated Apr 25, 2026

Search Tags:#automation #testing #verification #build #evidence #quality-assurance #claims

Ready to run

npx skills add https://github.com/mnsgrosa/skills --skill verification-before-completion-mnsgrosa

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification risks dishonesty and downstream rework; this Skill ensures every completion claim is backed by fresh verification evidence collected through a deliberate, repeatable process.

Core Features & Use Cases

Gate-driven verification: identify a verification command, run it in full, read the outputs, verify results, and only then claim completion.
Applies to software delivery workflows (CI, PRs, tests, builds) and any process that requires auditable proof of success.
Use Case: before closing a ticket, run the full verification suite and attach the evidence to the ticket or PR.

Quick Start

Identify the verification command, execute it fully, review the output, confirm success, and only then declare completion with evidence.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is build verification evidence and why do I need it before claiming task completion?▼

Build verification evidence is fresh output from running tests, linting, or builds that proves a task succeeded. You need it to prevent dishonest completion claims, avoid downstream rework, and provide auditable proof of success for quality assurance.

How do I verify test results before closing a pull request?▼

To verify test results before closing a pull request, identify your verification command, execute it fully, read the outputs, confirm success, and only then declare completion with the attached evidence.

Does this verification workflow handle build failures and linting errors explicitly?▼

Yes, this verification workflow handles build failures and linting errors explicitly through a five-step governance process that includes explicit failure handling and requires reading outputs before making any success claim.

What's the best way to automate quality assurance claims for CI pipelines?▼

The best way to automate quality assurance claims for CI pipelines is applying a gate-driven workflow that requires running verification commands, reading outputs, and attaching auditable evidence before any completion claim is accepted.

Can I use this verification process for non-software delivery tasks requiring auditable proof?▼

Yes, you can use this verification process for any non-software delivery tasks requiring auditable proof, as it enforces a deliberate, repeatable five-step process applicable to any workflow needing verified success assertions.

What are the limitations of using a gate-driven verification workflow?▼

A limitation of a gate-driven verification workflow is that it strictly prohibits claiming completion without fresh verification evidence, meaning you cannot bypass the five-step process even for minor tasks or rapid iterations.