verification-before-completion

Run verification commands and analyze output before declaring task completion.

8|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/hxk622/TokenDance --skill verification-before-completion-hxk622
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/hxk622/TokenDance/tree/main/backend/app/skills/builtin/superpowers/verification-before-completion
Command: npx skills add https://github.com/hxk622/TokenDance --skill verification-before-completion-hxk622

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the premature declaration of task completion or success by enforcing a strict verification process, ensuring that claims are backed by concrete evidence before being made.

Core Features & Use Cases

  • Mandatory Verification: Ensures that verification commands are run and their outputs are reviewed before any claim of success or completion.
  • Red Flag Identification: Helps identify and prevent common rationalizations for skipping verification.
  • Use Case: Before committing code changes, the agent must run the test suite and confirm zero failures, presenting the output as proof of completion.

Quick Start

Run the verification command and confirm the output before claiming the task is complete.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I prevent an AI agent from claiming a coding task is complete without running tests?

To prevent premature task completion, enforce a strict verification protocol requiring the agent to run specific commands like test suites and analyze their output to confirm zero failures before declaring success.

What is an evidence before claims protocol for code quality assurance?

An evidence before claims protocol is a verification process that mandates running testing or linting commands and reviewing their concrete output to substantiate any assertions of bug fixing or task completion.

How do I enforce mandatory verification before code completion?

You enforce mandatory verification by requiring the execution of specific testing or linting commands and analyzing their output to identify red flags or rationalizations before allowing any success declarations.

Can I use this verification process for both linting and bug fixing workflows?

Yes, you can use this verification process for both linting and bug fixing workflows, as the protocol applies to all stages of work by requiring concrete command output as proof before making any claims.

What are common red flags for skipping verification before task completion?

Common red flags include rationalizations for skipping the verification process, such as assuming code changes are safe without running the test suite or presenting assertions without concrete command output as evidence.