verification-before-completion

Enforce verification commands before asserting completion in development and QA workflows.

3|5|Updated Apr 26, 2026

Search Tags:#verification #completion #quality-assurance #process #lint #ci #tests

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preventing premature completion claims by enforcing verification before confirmation. This approach ensures evidence-based completion and reduces risk of shipping incomplete work.

Core Features & Use Cases

Enforces a step-by-step verification gate before any completion claim.
Applies to development and QA workflows where claims of passing tests, lint, or readiness must be supported by verifiable results.
Use case: Before creating a PR, run verification commands and cite fresh outputs as evidence.

Quick Start

Run the verification command, read the fresh output, and confirm it proves completion before asserting success.

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 development completion?▼

Enforce verification by running test and lint commands, inspecting the fresh output, and citing those results as evidence before asserting success. This prevents premature completion claims in QA workflows.

What is evidence-based completion in software engineering?▼

Evidence-based completion requires executing verification commands and inspecting their outputs to prove readiness. It reduces the risk of shipping incomplete work by backing claims with verifiable results.

How do I prevent premature completion claims in CI workflows?▼

Prevent premature completion by applying a verification gate in CI workflows. Run the required commands, read the output, and confirm it proves readiness before allowing a PR or success assertion.

Do I need to run tests and lint before creating a pull request?▼

Yes, you need to run tests and lint before creating a pull request to ensure readiness. The process requires executing verification commands and citing fresh outputs as evidence of completion.

What is the best way to gate pull requests on passing tests?▼

The best way to gate pull requests is enforcing a step-by-step verification process. Require running tests and lint, inspecting the fresh output, and only confirming success when verifiable results prove it.

Why does asserting task readiness without output inspection fail?▼

Asserting readiness without output inspection fails because it lacks verifiable results. Claiming tests pass without executing commands and inspecting outputs risks shipping incomplete work and bypassing quality assurance.