verification-before-completion

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

Enforce evidence-backed verification of tests, linting, and builds before completion.

1|2|Updated Jan 7, 2026

Search Tags:#workflow #verification #evidence #quality-assurance #process #gate-keeping

Ready to run

npx skills add https://github.com/danieldekay/copilot-config-promptops --skill verification-before-completion-danieldekay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/danieldekay/copilot-config-promptops/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/danieldekay/copilot-config-promptops --skill verification-before-completion-danieldekay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claims of completion without verification are dishonest and wasteful. This Skill enforces an evidence-backed verification workflow before any completion claim, ensuring that results are reproducible and verifiable.

Core Features & Use Cases

Enforces a stepwise verification routine: IDENTIFY, RUN, READ, VERIFY, ONLY THEN.
Reduces risk of false positives in tests, builds, and handoffs by requiring fresh evidence.
Use Case: teams that must confirm test and build results before merging, releasing, or closing work items.

Quick Start

Follow the verification workflow to confirm success: IDENTIFY the command to prove the claim, RUN the full verification, READ the output, VERIFY the results, and ONLY THEN claim 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 verification before marking a software build as complete?▼

To enforce verification before marking a software build as complete, implement a stepwise workflow that requires running explicit commands, reading fresh output, and validating results against expected criteria before claiming success.

What is an evidence-backed verification workflow for QA handoffs?▼

An evidence-backed verification workflow for QA handoffs is a deterministic process requiring fresh test and linting outputs to validate success, preventing false positives by ensuring results are reproducible before work items are closed.

How do I prevent premature completion claims in software development?▼

Prevent premature completion claims in software development by applying a gate-keeping routine that identifies verification commands, runs full checks, and validates actual outputs against expected criteria before any success is claimed.

Does project handoff verification require explicit commands and expected outputs?▼

Yes, project handoff verification requires explicit commands and expected outputs to validate success deterministically, ensuring that test and build results are reproducible and verifiable before merging or releasing work.

What is the best way to verify test results before merging code?▼

The best way to verify test results before merging code is to follow a strict verification routine: identify the proof command, run the full test suite, read the output, and verify results match expected criteria before claiming completion.

When should I not use an automated verification gate-keeping process?▼

You should not use an automated verification gate-keeping process when you lack deterministic commands, expected outputs, or clear criteria to validate success, as the workflow requires explicit evidence to prevent false positives in builds and handoffs.