verification-before-completion

Enforce a verification gate before declaring project tasks complete.

3|Updated Dec 30, 2025

Search Tags:#verification #governance #code-quality #gating #release-process #test-verification

Ready to run

npx skills add https://github.com/martin-janci/claude-marketplace --skill verification-before-completion-martin-janci

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/martin-janci/claude-marketplace/tree/main/plugins/dev-agents/skills/verification-before-completion
Command: npx skills add https://github.com/martin-janci/claude-marketplace --skill verification-before-completion-martin-janci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification is dishonesty, not efficiency.

Core Features & Use Cases

Enforces a verification gate before declaring completion
Guides teams through a structured run-read-verify workflow
Improves auditability and trust in release readiness

Quick Start

Run the verification command, review the full output, and report evidence before claiming 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 a verification gate before marking a build or test as complete?▼

Enforce a verification gate by requiring fresh evidence before completion claims. A structured run-read-verify workflow mandates executing a concrete verification command, reviewing the full output, and reporting evidence to satisfy release readiness checks.

What does it mean to require fresh verification evidence for release readiness?▼

Requiring fresh verification evidence means validating tasks, tests, or builds with current output before declaring completion. This process prevents deception by enforcing a concrete verification command and evidence-based reporting for auditability.

How do I verify test completion claims to improve governance and auditability?▼

Verify test completion claims by applying an evidence-based reporting workflow. Guide teams through running a verification command, reviewing full output, and validating results before marking tasks done to satisfy governance requirements and improve trust.

Can I use a structured verification workflow for project tasks without external dependencies?▼

Yes, you can apply this verification workflow to project tasks without external dependencies. It operates as an intermediate-level gating mechanism within project workflows, requiring only a concrete verification command and full-output review to validate completion.

What is the best way to prevent unverified code from passing the release process?▼

The best way to prevent unverified code from passing the release process is enforcing a gating mechanism. Require running a verification command, reviewing full output, and gathering fresh evidence before allowing any completion or release readiness claims.

Why does claiming work as complete without verification cause governance issues?▼

Claiming work as complete without verification causes governance issues because it bypasses evidence-based validation. This practice introduces dishonesty into the release process by skipping the required test verification and full-output review needed for auditability.