verification-before-completion

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

Execute verification commands and analyze output before declaring task completion.

2|Updated Apr 6, 2026

Search Tags:#testing #validation #verification #quality-assurance #accountability

Ready to run

npx skills add https://github.com/dascard/nanobot --skill verification-before-completion-dascard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/dascard/nanobot/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/dascard/nanobot --skill verification-before-completion-dascard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of prematurely declaring work as finished without actual proof, ensuring that all claims of success are backed by verifiable evidence.

Core Features & Use Cases

Evidence-Based Validation: Mandates the execution of specific verification commands before any status update.
Failure Pattern Mitigation: Actively identifies and blocks common excuses like relying on assumptions, partial checks, or unverified agent reports.
Use Case: Before submitting a pull request or marking a task as done, use this skill to run the full test suite and confirm the output matches the expected success criteria.

Quick Start

Run the verification-before-completion skill to validate the current task status by executing the necessary test commands and confirming the output.

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 evidence-based validation before marking a task as complete?▼

Evidence-based validation requires executing specific verification commands and analyzing their output to confirm state changes before declaring task completion. This mitigates failure patterns by blocking assumptions and unverified reports.

What is the best way to prevent premature task completion in software development workflows?▼

Preventing premature task completion requires rigorous verification protocols that mandate objective evidence of state changes. This approach blocks partial checks and enforces accountability before success is declared.

How do I run validation commands to verify task status before submitting a pull request?▼

Run the verification protocols to execute necessary test commands and confirm the output matches expected success criteria. This validates the current task status by requiring objective evidence before submission.

Does evidence-based verification work for project management workflows that require objective proof?▼

Yes, evidence-based verification applies to project management workflows by requiring the execution of specific validation commands and analysis of their output to confirm state changes before task success is declared.

Why do I need to verify output matches expected success criteria before declaring task completion?▼

Verifying output matches expected success criteria is necessary to prevent prematurely declaring work as finished without actual proof. It ensures all claims of success are backed by verifiable evidence.

What limitations exist when relying on partial checks instead of full test suite verification?▼

Relying on partial checks instead of full test suite verification leads to failure patterns like assumptions and unverified agent reports. These limitations are actively identified and blocked by rigorous verification protocols.