verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: coctostan

Run verification commands and inspect full output before claiming completion.

69|9|Updated Feb 8, 2026

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

Ready to run

npx skills add https://github.com/coctostan/pi-superpowers --skill verification-before-completion-coctostan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unverified completion claims by enforcing a fresh verification process before declaring work complete, ensuring evidence-based progress.

Core Features & Use Cases

Enforces a strict verification workflow that requires identifying the proving command, running it, reading the full output, and verifying results before any success claim.
Applicable to software development tasks, pull requests, and release checks where completion status must be validated with verifiable evidence.
Supports safer handoffs and auditing by providing a transparent, repeatable verification protocol.

Quick Start

Run the verification workflow to run the full verification command, inspect results, and only then claim completion 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 enforce verification before claiming a software task is complete?▼

Enforcing verification before completion requires identifying a proving command, running it, and evaluating the full output to validate success. This process prevents unverified completion claims by demanding verifiable evidence like passing tests and successful builds.

What is evidence-based completion in software development?▼

Evidence-based completion in software development is a strict protocol requiring fresh verification before declaring work done. It ensures progress claims are validated with verifiable evidence from tests, linting, and builds rather than assumptions.

How do I verify pull request readiness with a repeatable protocol?▼

To verify pull request readiness, execute a verification command and inspect its full output to confirm success. This repeatable protocol supports safer handoffs and auditing by preventing unverified completion claims with transparent evidence.

Can I use this verification workflow for release readiness checks?▼

Yes, this verification workflow applies to release checks where completion status must be validated. It enforces running proving commands and evaluating results to ensure tests, linting, and builds succeed before making any success claim.

Why does declaring work complete without fresh verification cause problems?▼

Declaring work complete without fresh verification causes problems by allowing unverified success claims to propagate. Enforcing a strict verification workflow prevents this by requiring tests, linting, and builds to be validated with verifiable evidence before completion.

What's the best way to prevent unverified completion claims in CI-CD?▼

The best way to prevent unverified completion claims in CI-CD is enforcing a strict workflow that requires identifying the proving command, running it, reading the full output, and verifying results before any success claim is made.