verification-before-completion

Run verification commands and confirm output before claiming work completion.

5|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/primatrix/skills --skill verification-before-completion-primatrix
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/primatrix/skills/tree/main/plugins/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/primatrix/skills --skill verification-before-completion-primatrix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that before making claims of work completion or success, proper verification is performed, mitigating the risk of releasing incorrect or incomplete work.

Core Features & Use Cases

  • Verification Protocols: Implement strict verification steps to validate work claims.
  • Gate Function: Follows a gate function with clear steps to claim completion, including identification, running, reading, and verifying output.
  • Preventing Rationalization: Identifies common rationalization excuses and provides solutions to prevent them.

Quick Start

Run 'verify-work' to check the verification status of your latest changes and ensure you are ready to commit or create a PR.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify work completion before making a commit or pull request?▼

Work verification before a commit or pull request requires running verification commands and confirming their output. This protocol acts as a quality gate to ensure the accuracy and completeness of your work claims before integration.

What is a verification protocol for pre-commit work integrity?▼

A pre-commit verification protocol is a strict gate function that identifies, runs, and reads verification commands to validate work claims. It prevents rationalization excuses by enforcing concrete output confirmation before allowing completion claims.

How do I prevent rationalization excuses when claiming work is done?▼

Preventing rationalization excuses involves following a strict verification gate function that requires identifying, running, and reading verification command outputs. This enforces objective proof of work integrity over subjective assumptions of completion.

Can I use this pre-Pull Request verification gate for any software engineering task?▼

Yes, this verification gate applies to general software engineering tasks at pre-commit or pre-Pull Request stages. It requires no specific dependencies or component setups to validate work readiness and claim accuracy.

What are the limitations of using verification commands for commit readiness?▼

The limitation of using verification commands for commit readiness is that the protocol only validates the execution and output of specified commands. It does not replace manual code review but ensures objective work integrity before claiming completion.