verification-before-completion

Run a defined verification sequence and present evidence before reporting completion.

12|2|Updated Mar 22, 2026

Search Tags:#verification #completion #build #evidence #ci #tests

Ready to run

npx skills add https://github.com/aman-2709/superpowers-ecc --skill verification-before-completion-aman-2709

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification is dishonest and error-prone. This skill enforces evidence-based claims by requiring fresh verification outputs before declaring success.

Core Features & Use Cases

Enforces a structured verification gate before commits, PRs, or releases.
Guides users through identify-run-read-verify steps to ensure claims are grounded in evidence.
Useful in CI workflows, code reviews, and feature delivery where truthfulness and traceability matter.

Quick Start

Before declaring completion, run the verification steps and attach the 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 prevent claiming a build is complete without verification evidence?▼

To prevent claiming build completion without verification evidence, enforce a structured verification gate requiring fresh outputs from tests or CI checks before declaring success.

What steps should I follow to verify CI tests before a pull request?▼

To verify CI tests before a pull request, execute a defined sequence: identify required checks, run tests, read outputs, verify results, and report explicit evidence.

When do I need to attach fresh verification outputs to release readiness checks?▼

You need fresh verification outputs for release readiness checks whenever claiming tests, builds, or feature delivery success to ensure traceability and prevent error-prone declarations.

Can I use evidence-based verification workflows for code reviews?▼

Yes, you can use evidence-based verification workflows for code reviews. They guide users through identify-run-read-verify steps to ensure completion claims are grounded in fresh outputs.

What happens if I report completion without running a defined verification sequence?▼

Reporting completion without running a defined verification sequence bypasses the evidence gate, leading to dishonest, error-prone claims that lack traceability for CI and PR checks.