verification-before-completion

Enforces verification before declaring tasks complete by requiring fresh evidence from tests, builds, or lint.

4|1|Updated Feb 3, 2026

Search Tags:#qa #verification #completion #governance #evidence #ci-cd

Ready to run

npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill verification-before-completion-lespaceman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/lespaceman/athena-workflow-marketplace/tree/main/plugins/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/lespaceman/athena-workflow-marketplace --skill verification-before-completion-lespaceman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification hides defects, misleads stakeholders, and erodes trust. This skill enforces a formal verification gate that requires fresh evidence from the actual verification commands before assertions of completion.

Core Features & Use Cases

Enforces running verification commands (tests, builds, lint, type checks) before declaring completion.
Requires evidence (logs, exit codes, artifacts) to support completion claims.
Use Case: In a software project, gate a PR merge or deployment on successful verification with visible results.

Quick Start

Run the verification command suite and attach the results to your 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 steps before declaring a task complete?▼

To enforce verification before completion, you must execute verification commands like tests, builds, lint, or type checks and attach fresh evidence of the results. This prevents premature success claims by gating the completion status on actual command outputs.

What is a verification gate in CI/CD and software governance?▼

A verification gate in software governance is a formal checkpoint requiring fresh evidence from actual verification commands before task completion is declared. It ensures claims of done work are backed by executed tests, builds, or lint results to prevent hidden defects.

How do I prevent premature success claims during software development or operational tasks?▼

Prevent premature success claims by requiring fresh evidence such as logs, exit codes, and artifacts from verification commands. Gating task completion on these visible results ensures stakeholders are not misled by unverified work passing as complete.

Can I gate a pull request merge on successful verification with visible results?▼

Yes, you can gate a PR merge or deployment by requiring successful execution of verification commands with visible results. This ensures that fresh evidence from tests, builds, or lint checks is attached before the work is marked complete.

Does verification before completion work for data tasks and operational work?▼

Verification before completion applies across software development, data tasks, and operational work. It requires executing verification steps and attaching fresh evidence like exit codes or logs before marking any work as done, ensuring accuracy across domains.

What limitations exist when requiring fresh evidence for completion claims?▼

The primary limitation is that fresh evidence requires actually executing verification commands like tests or builds. If the environment cannot run these checks or generate artifacts and exit codes, the completion gate cannot be satisfied.