Verification Before Completion

Require fresh verification evidence before claiming task completion.

8|2|Updated Jul 13, 2015

Search Tags:#verification #governance #evidence #quality-assurance #output #claims

Ready to run

npx skills add https://github.com/tstapler/dotfiles --skill verification-before-completion-tstapler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Verification Before Completion
Source: https://github.com/tstapler/dotfiles/tree/main/.claude/skills/debugging/verification-before-completion
Command: npx skills add https://github.com/tstapler/dotfiles --skill verification-before-completion-tstapler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This policy enforces verification before making completion claims to ensure every claim is backed by fresh evidence, reducing dishonesty and rework.

Core Features & Use Cases

Define the verification steps that prove a task is complete.
Run fresh checks against the full command output and exit status, then interpret results against a success criterion.
Use before committing, creating PRs, or announcing completion to prevent premature or unsupported claims.

Quick Start

Before claiming completion, run the verification command(s) and present fresh output as evidence.

Frequently Asked Questions about Verification Before Completion

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

FAQPage Schema

How do I verify task completion before creating a pull request?▼

To verify task completion before creating a pull request, define explicit verification commands, execute them fully, and present fresh output as evidence against a success criterion. This prevents unsupported completion claims and reduces rework by validating results.

What is evidence-based reporting in software quality assurance?▼

Evidence-based reporting in software quality assurance is the practice of validating completion claims by running fresh checks against full command output and exit status. It ensures every claim of task completion is backed by explicit, up-to-date verification evidence.

When do I need to enforce verification steps for project governance?▼

You need to enforce verification steps for project governance when making completion claims, committing code, or creating PRs. It is required in software development and QA tasks to prevent premature announcements and ensure all claims are validated with fresh evidence.

Does this verification approach work without external dependencies?▼

Yes, this verification approach works without external dependencies. It is a standalone policy that enforces verification by requiring explicit commands to be executed fully within your current environment, interpreting the exit status and output against defined success criteria.

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

The best way to prevent premature completion claims in software development is to enforce a policy requiring fresh evidence before announcing completion. Run explicit verification commands, check the full output and exit status, and interpret results against a success criterion.

Why does claiming completion without fresh evidence cause rework?▼

Claiming completion without fresh evidence causes rework because unvalidated claims often hide unresolved issues. By enforcing explicit verification commands and interpreting full output against success criteria, you catch failures early and prevent dishonest or unsupported completion claims.