verification-before-completion

Run full verification commands before declaring completion claims.

4|1|Updated Apr 7, 2026

Search Tags:#testing #code review #verification #compliance #quality-gate #dev workflow

Ready to run

npx skills add https://github.com/NSObjects/specpowers --skill verification-before-completion-nsobjects

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/NSObjects/specpowers/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/NSObjects/specpowers --skill verification-before-completion-nsobjects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature completion claims by enforcing verification, so every success statement is backed by fresh command output evidence.

Core Features & Use Cases

Verification Gatekeeping: Requires identifying, running, and inspecting the full verification command before declaring tests, builds, or fixes done.
Evidence-first Communication: Teaches agents and collaborators to report exact outputs, exit codes, and failure counts instead of vague confidence.
Quality Gate Integration: Encourages running the quality-gate skill for linting, formatting, and type safety checks as the automatic source of clean-state evidence.

Quick Start

Tell the assistant to run the relevant verification command and report its output before claiming success.

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 running tests before declaring a task complete?▼

To enforce verification before completion, use a quality gate that requires running full test commands and inspecting their output prior to any phase transition. This prevents premature completion claims by demanding fresh command output evidence for every success statement.

What is the best way to verify code review compliance before a commit?▼

Verifying compliance before a commit involves running linting, formatting, and type safety checks to ensure a clean state. You must execute these quality gates and cite concrete command outputs, exit codes, and failure counts instead of relying on vague confidence.

How do I prevent AI agents from making false success claims during dev workflows?▼

To prevent false success claims in dev workflows, mandate evidence-first communication by requiring agents to report exact outputs and exit codes. Enforce a verification gate so agents must run and inspect full commands before claiming tests or builds are done.

When do I need to run a quality gate check during a pull request?▼

You need to run a quality gate check during a pull request when transitioning phases or declaring a fix complete. This ensures that tests, linting, and builds have been freshly executed and verified with concrete output evidence before completion.

Does claiming a build is done require showing command output evidence?▼

Yes, claiming a build is done requires showing command output evidence. The verification process enforces evidence-first communication, demanding that you run the full verification command and report exact outputs, exit codes, and failure counts to substantiate passing assertions.