verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: Postalocity

Enforce fresh verification evidence before reporting task completion.

1|Updated Mar 5, 2026

Search Tags:#verification #completion #evidence #quality-assurance #code-review #gate-function

Ready to run

npx skills add https://github.com/Postalocity/template-microsite --skill verification-before-completion-postalocity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Postalocity/template-microsite/tree/main/.opencode/skills/superpowers--verification-before-completion
Command: npx skills add https://github.com/Postalocity/template-microsite --skill verification-before-completion-postalocity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification is dishonest and inefficient. This Skill enforces evidence-based claims by requiring fresh verification outputs before declaring success, guarding against misstatements and regressions.

Core Features & Use Cases

Enforces a gate-style workflow where the claim is only valid after running a full verification command and validating its output.
Provides a repeatable, auditable process for code reviews, PRs, and task completion in development workflows.
Useful in any scenario where outcomes must be proven with verifiable evidence to prevent premature or inaccurate assertions.

Quick Start

Run the full verification command in the current context and provide the exact verification output as the evidence before confirming completion.

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 code review verification before claiming task completion?▼

Code review verification before claiming completion requires running a full verification command and validating its fresh output artifacts to prove the result, preventing premature or inaccurate success claims.

What is evidence-based verification for pull requests?▼

Evidence-based verification for pull requests is a gate-style workflow enforcing fresh verification outputs before declaring success, ensuring development outcomes are proven with auditable artifacts.

How do I stop reporting success before verifying code changes?▼

To stop reporting success prematurely, apply a gate function protocol that identifies the verification command, executes it fully, reads the output, and only publishes the result after validation.

Can I use this verification gate for general software development tasks?▼

Yes, this verification gate applies to general software development tasks, code reviews, and pull requests where outputs must be proven with fresh verifiable evidence before reporting success.

Why does claiming completion without verification cause regressions?▼

Claiming completion without verification causes regressions because unverified assertions bypass quality assurance checks, allowing misstatements and code regressions to be published as successful outcomes.

What's the best way to require proof of completion for development workflows?▼

The best way to require proof of completion is enforcing a repeatable, auditable gate-style process that demands fresh verification evidence from executed commands before approving any development workflow result.