verification-before-completion

Run verification commands and inspect outputs before declaring task completion.

9|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/hongmaple0820/agent-academy --skill verification-before-completion-hongmaple0820
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/hongmaple0820/agent-academy/tree/main/skills/development/verification-before-completion
Command: npx skills add https://github.com/hongmaple0820/agent-academy --skill verification-before-completion-hongmaple0820

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents premature completion claims by requiring verifiable evidence before asserting success, reducing misstatements and rework.

Core Features & Use Cases

  • Enforces running a verification command and inspecting full outputs before declaring a task complete.
  • Applies to code reviews, pull requests, builds, and any task with verifiable criteria.
  • Helps teams maintain trust and improve release quality by ensuring evidence-backed claims.

Quick Start

Run the verification command to generate fresh results, review the full output for accuracy, and only declare completion when the evidence confirms 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 prevent premature completion claims during code reviews?

Prevent premature completion claims by enforcing verification checkpoints that require running a verification command and inspecting full outputs before declaring a task complete.

What is evidence-backed verification for pull requests?

Evidence-backed verification is a process check that requires running verification commands, reviewing full outputs, and only asserting task completion when the evidence confirms success.

How do I enforce verification checkpoints for builds and pull requests?

Enforce verification checkpoints by running the verification command to generate fresh results, reviewing the full output for accuracy, and only declaring completion when evidence confirms success.

Does this process check approach work for general software tasks?

Yes, this process check applies to software tasks, code reviews, builds, and pull requests where verifiable criteria and verification checkpoints are needed to ensure quality.

Why do I need verifiable evidence before declaring task success?

You need verifiable evidence before declaring task success to reduce misstatements, prevent rework, and help teams maintain trust by ensuring evidence-backed claims.

What are the limitations of manual quality assurance gatekeeping?

Manual quality assurance gatekeeping lacks enforced verification, allowing premature completion claims without inspecting full command outputs, which increases misstatements and rework.