verification-before-completion

Require fresh command output before asserting tests, builds, or fixes pass.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill verification-before-completion-enigmaicon-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill verification-before-completion-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false completion claims by forcing you to verify results with fresh, complete command output before you state work is finished or correct.

Core Features & Use Cases

  • Evidence-first completion gate: Requires identifying the exact verification command, running the full command, and validating the output before any success or satisfaction statement.
  • Consistency across claims: Covers tests, linting, builds, bug fixes, regression verification, and requirement checklists so “done” is backed by observable evidence.
  • Red-flag and anti-rationalization guardrails: Blocks common failure patterns like trusting an agent’s success report, using “should/probably,” or claiming completion after partial checks; instead, it directs you to stop and re-run verification.

Quick Start

Use the skill when you are about to claim something is complete or passing by running the relevant full verification command and only then stating the result with 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 false completion claims in CI/CD and pull requests?

You can enforce an evidence-first completion gate by mandating exact command selection, running the full verification, and validating the actual output before allowing any success statement for tests, linting, or builds.

How do I verify a bug fix is actually resolved before reporting status?

To verify a bug fix before reporting status, you must run the complete regression verification command and inspect the actual exit code and output, rejecting any success wording until fresh evidence is obtained.

What is evidence-based status reporting in software engineering governance?

Evidence-based status reporting is a governance gate function that mandates substantiating correctness with actual command output and exit codes, rejecting completion claims based on partial checks or unverified agent reports.

Why does my agent report a task is passing when the test execution fails?

An agent may report a task is passing when test execution fails due to rationalization patterns like trusting partial checks or using "should/probably" wording, which this verification gate blocks by mandating fresh output inspection.

Can I claim a requirement is satisfied without running the full verification command?

No, you cannot claim a requirement is satisfied without running the full verification command. This governance mechanism rejects success wording without verification and directs you to stop and re-run the evidence collection.