skills.rest
costrict-plugins-repo
costrict-plugins-repoOFFICIAL
Explore all skills by this author →
GitHub

verification-before-completion

Enforce verification commands before reporting completion status in workflows.

Updated May 19, 2026
Search Tags:#verification#completion#evidence#code-review#ci#tests
One-click install
npx skills add https://github.com/costrict-plugins-repo/anthropic-superpowers --skill verification-before-completion-costrict-plugins-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/costrict-plugins-repo/anthropic-superpowers/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/costrict-plugins-repo/anthropic-superpowers --skill verification-before-completion-costrict-plugins-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification leads to unreliable software; this skill enforces verification before making success claims and requires fresh evidence.

Core Features & Use Cases

  • Enforces an evidence-before-claims protocol across development workflows.
  • Guides teams to run verification commands, interpret outputs, and produce defensible status updates.
  • Suitable for PR reviews, releases, and handoffs where verification is critical.

Quick Start

Run the full verification command set and report the outputs before asserting 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 verification before claiming code review completion?▼

To enforce verification before claiming code review completion, execute fresh verification commands, evaluate the outputs, and report a defensible status update. This protocol requires evidence-backed decisions before advancing any PR or release workflow.

Why does premature completion claiming happen and how do I prevent it?▼

Premature completion claiming happens when status updates lack evidence, leading to unreliable software. Prevent it by running fresh verification commands, interpreting the test outputs, and producing a defensible status report before advancing any work.

What's the best way to verify code changes before a release handoff?▼

The best way to verify code changes before a release handoff is to run the full verification command set, interpret the outputs, and produce an evidence-backed status update. This ensures defensible decisions before advancing the release workflow.

Can I use this verification protocol for CI tests and PR reviews?▼

Yes, you can use this verification protocol for CI tests and PR reviews. It enforces an evidence-before-claims protocol across development workflows, requiring fresh test execution and output evaluation before advancing any status updates.

How do I generate defensible status updates for development workflows?▼

Generate defensible status updates for development workflows by executing fresh verification commands and evaluating the outputs. Evidence-backed decisions are required before asserting any task completion or advancing code changes.

Related Skills

Explore More Software Engineering Skills→
krzemienskikrzemienski
2

verification-before-completion

Require fresh verification evidence before declaring task completion.

Community
Advanced
yanochka11yanochka11

verification-before-completion

Require fresh verification evidence before reporting software tasks as complete.

Community
Intermediate
jagreehaljagreehal
3

verification-before-completion

Run verification commands and report outputs before completion claims.

Community
Intermediate
ajsai47ajsai47
11

requesting-code-review

Dispatches a dedicated reviewer to inspect code changes and categorize severity of defects.

Community
Intermediate