verification-before-completion

Run verification commands and report evidence before marking work complete.

70|6|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/earchibald/vsc-superpowers --skill verification-before-completion-earchibald
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/earchibald/vsc-superpowers/tree/main/.agents/skills/verify
Command: npx skills add https://github.com/earchibald/vsc-superpowers --skill verification-before-completion-earchibald

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure claims of completion are backed by fresh verification evidence, preventing premature status updates and misrepresentation.

Core Features & Use Cases

  • Step-by-step guardrail to verify results before marking work complete.
  • Applies to commits, PRs, and agent-delivered tasks to ensure completion is supported by evidence and test results.
  • Provides a deterministic verification pattern and evidence requirements.

Quick Start

Run the full verification command and report the result with 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 verify task completion before claiming a PR is ready?

To verify task completion, identify the specific verification command, execute it, inspect the outputs, and report the results with evidence before marking any PR or commit as complete.

What is the best way to ensure agent-driven tasks have evidence before reporting success?

Enforcing a deterministic verification pattern ensures agent-driven tasks have evidence by requiring test commands to run and outputs to be inspected before any completion status is reported.

How do I prevent premature status updates on commits and pull requests?

You can prevent premature status updates by applying a step-by-step guardrail that executes verification commands and gathers fresh test result evidence before a completion status is claimed.

Does CI-CD quality assurance require explicit verification steps for every task?

Yes, CI-CD quality assurance requires explicit verification steps for every task to ensure completion claims are backed by fresh evidence and deterministic test results rather than assumptions.

What are the limitations of claiming completion without running verification commands?

Claiming completion without running verification commands risks misrepresentation and premature status updates because outcomes lack the support of fresh evidence or actual test results.