verification-before-completion

Execute verification commands and validate outputs before declaring work complete.

Updated May 19, 2026

Search Tags:#verification #evidence #quality-assurance #software-development #workflows #decision-control

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonest, not efficient. This Skill enforces evidence-first completion to prevent premature success claims and guard against misreporting.

Core Features & Use Cases

Gate-based verification: require explicit verification steps and evidence before status updates, commits or PRs.
Common patterns: identifies required commands, executes them, and validates outputs to decide if work can be considered done.
Use Case: a developer finishes a feature only after running the full test suite and verifying all results before opening a PR.

Quick Start

Run the verification command with fresh outputs and claim completion only when results are fully verified.

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

You can enforce verification before completion by requiring explicit evidence, such as executing commands and validating outputs, before allowing status updates or PR claims. This gate-based approach prevents premature success claims and misreporting.

What is evidence-first completion in software development workflows?▼

Evidence-first completion is a quality-assurance process where a developer must run required commands, read the fresh outputs, and validate the results against success criteria before marking a task or PR as done.

How do I stop premature success claims in pull requests?▼

To stop premature success claims in pull requests, implement a decision-control gate that blocks commits until the full test suite is executed and all outputs are fully verified, ensuring claims of completion are backed by evidence.

Can I gate status updates behind successful test suite execution?▼

Yes, you can gate status updates by identifying required verification commands, executing them to generate fresh outputs, and only allowing the status change when the results fully meet the declared success criteria.

What's the best way to verify work before opening a pull request?▼

The best way to verify work before opening a pull request is to run the full test suite, read the command outputs, and confirm all results are successful, claiming completion only when the evidence is fully verified.

Why does claiming work is complete without verification cause problems in software development?▼

Claiming work is complete without verification causes problems because it is dishonest and introduces misreporting into software development workflows, leading to trust issues and unverified code being committed or merged.