verification-before-completion

Run full verification commands and report evidence before completion claims.

Updated Feb 14, 2026

Search Tags:#verification #quality-assurance #process #guardrails #claims #pull-request

Ready to run

npx skills add https://github.com/jbro/pi-agent --skill verification-before-completion-jbro

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that any claim of completion or success is backed by verifiable evidence, eliminating premature or dishonest assertions in workflows.

Core Features & Use Cases

Enforce a structured verification before declaring work complete.
Provide step-by-step checks, such as running tests, linters, or validations, and interpreting results.
Use Case: before merging a PR or closing a ticket, verify all required checks and attach concrete evidence.

Quick Start

Run the full verification command and attach its verifiable results before making any completion claim.

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 checks before closing a pull request?▼

To enforce verification before closing a pull request, run full validation commands like tests and linters, interpret the outputs, and attach concrete evidence prior to making any completion claim.

What is the best way to prevent premature completion claims in software engineering workflows?▼

Preventing premature completion claims requires a structured verification process that executes checks on code changes and documentation, demanding irrefutable evidence before allowing any success statements or ticket closures.

How do I verify code changes and documentation updates before declaring a task complete?▼

Verify code changes and documentation updates by executing step-by-step checks, interpreting the validation results, and reporting the evidence to satisfy requirements prior to declaring a task complete.

Can I use structured verification for post-implementation checks and releases?▼

Yes, structured verification applies to post-implementation checks and releases, enforcing the execution of full verification commands and interpretation of outputs before any success assertions are made.

Why do I need to attach verifiable evidence before claiming a release is successful?▼

Attaching verifiable evidence before claiming a release is successful eliminates dishonest assertions by ensuring all required checks are executed, interpreted, and reported prior to any success statements.

Does verification before completion work without external dependencies?▼

Yes, verification before completion works without external dependencies, using its advanced internal reasoning to enforce guardrails and interpret validation outputs directly within your workflow.