verification-before-completion

Verify command outputs and test results before claiming task completion.

2|Updated Mar 29, 2026

Search Tags:#testing #verification #reliability #quality-assurance #workflow-automation

Ready to run

npx skills add https://github.com/NagyVikt/codex-plugins --skill verification-before-completion-nagyvikt

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common AI failure of claiming work is finished or correct without actually verifying the results, which leads to broken code, missed requirements, and loss of trust.

Core Features & Use Cases

Verification Gatekeeping: Forces a mandatory check of command outputs, exit codes, and test results before any success claim is made.
Rationalization Prevention: Provides a structured framework to identify and reject common excuses for skipping verification steps.
Use Case: Before submitting a pull request or marking a task as done, use this skill to ensure you have run the full test suite and verified the build output against the actual requirements.

Quick Start

Run the verification-before-completion skill to audit your current progress and confirm that all necessary test commands have been executed with successful output before you finalize your response.

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 AI from claiming code is complete without running tests?▼

To prevent unverified AI claims, you enforce a verification gatekeeping protocol that checks command outputs, exit codes, and test results before any task completion claim. This ensures objective proof of work by requiring fresh execution of verification commands.

What is evidence-based work completion in software engineering?▼

Evidence-based work completion is a reliability protocol that mandates fresh execution and analysis of verification commands before claiming success. It prevents rationalization by enforcing a structured framework to reject excuses for skipping quality-assurance steps.

How do I enforce verification steps before submitting a pull request?▼

Enforce verification steps by running an audit protocol that confirms all necessary test commands have executed with successful output. This gatekeeping process checks test suite results and build output against actual requirements before finalizing any submission.

Does workflow automation for quality assurance require specific dependencies?▼

No, this workflow automation for quality assurance operates without external dependencies. It provides a structured reasoning framework applicable to all development, testing, and deployment workflows where objective accuracy and evidence are required.

Why does skipping verification protocols lead to broken code in deployment workflows?▼

Skipping verification protocols leads to broken code because it allows task completion claims without checking command outputs or test results. This rationalization introduces missed requirements and undetected failures into deployment workflows, causing loss of trust.

When should I not use automated verification gatekeeping?▼

Automated verification gatekeeping is strictly required for all development, testing, and deployment workflows demanding accuracy. You should not bypass it when objective proof of work, such as fresh command execution and output analysis, is necessary to confirm success.