verification-before-completion

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

Enforce a verification gate before claiming task completion.

6|Updated Dec 7, 2025

Search Tags:#testing #verification #QA #quality #governance #evidence #claims

Ready to run

npx skills add https://github.com/timequity/plugins --skill verification-before-completion-timequity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/timequity/plugins/tree/main/craft-coder/verification-before-completion
Command: npx skills add https://github.com/timequity/plugins --skill verification-before-completion-timequity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a disciplined process to verify outcomes before declaring work done, reducing over-claims and improving accountability.

Core Features & Use Cases

Verification Gate: A step-by-step ritual to run the full verification command and evaluate results.
Red/Green Patterns: Encourages regression-style verification to ensure fixes hold.
Claim Criteria: Clear criteria for what constitutes a completed task.

Quick Start

Define the verification command, run it fresh, and report the results before making any completion claim.

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 that a bug fix actually works before marking it complete?▼

Run the full verification command fresh—tests, builds, linting—after applying your fix. Read the results directly from the output, confirm the fix holds under regression testing, and only then claim completion. This prevents marking work done without evidence.

What's the best way to ensure quality claims are backed by evidence?▼

Enforce a verification gate: identify what needs testing, run the verification command, read the output yourself, verify the results match your claim criteria, then make your completion claim. This disciplined process reduces over-claims and improves accountability.

When should I run verification checks in my development workflow?▼

Run verification checks fresh at task completion, before release milestones, and whenever you claim a fix is done. Verification applies to tests, builds, linting, bug fixes, and governance checkpoints—any workflow context where completion requires evidence.

Can I verify my work without running the full test suite?▼

No. The verification gate requires running the complete verification command—tests, builds, linting, all steps—and reading the actual results. Partial checks create blind spots; fresh, full runs catch regressions and prevent unverified claims.

How do I know what verification evidence counts as 'complete'?▼

Define clear claim criteria upfront: what test pass rate, build status, or linting results constitute completion. Run verification fresh, evaluate results against those criteria, then report what you found. The evidence must exist before you claim the task is done.

Why does fresh verification matter if tests passed before?▼

Fresh verification catches regressions, environmental changes, and side effects introduced by recent work. Running the full suite again before claiming completion ensures your fix actually holds and hasn't broken something else.