verification-before-completion

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

Run verification commands and report evidence before claiming completion.

5|1|Updated Jan 26, 2026

Search Tags:#testing #verification #reporting #evidence #quality-assurance #CI #claims

Ready to run

npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill verification-before-completion-ed3dai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ed3dai/ed3d-plugins-testing/tree/main/plugins/ed3d-plan-and-execute/skills/verification-before-completion
Command: npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill verification-before-completion-ed3dai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces verification before claiming completion, ensuring every success claim is backed by verifiable evidence.

Core Features & Use Cases

Enforces a structured verification process before any completion claim (tests, builds, or deployments).
Guides teams through the Gate Function: identify command, run it, read outputs, verify results, and report with evidence.
Applies across development workflows to prevent dishonest or premature release claims.

Quick Start

Initiate a verification workflow by stating the claim to verify, run the required verification commands, review the outputs, and report the 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 verification before claiming a build or deployment is complete?▼

You can enforce verification before completion by running the required verification commands, parsing their outputs, and reporting fresh evidence to back every success claim regarding tests, builds, or deployments.

What is the Gate Function process for software quality assurance?▼

The Gate Function process for quality assurance requires you to identify the verification command, run it, read the outputs, verify the results, and report the evidence before making any success claim.

How do I collect fresh evidence for CI testing claims?▼

To collect fresh evidence for CI testing claims, state the claim to verify, run the required verification commands, review the outputs, and report the evidence before claiming completion.

Can I use this structured verification process for any development workflow?▼

Yes, you can use this structured verification process across development workflows where claims about tests, builds, or deployments must be backed by verifiable outputs to prevent premature releases.

Why do I need to parse command outputs for release verification?▼

Parsing command outputs for release verification is required to ensure every success claim is backed by verifiable evidence, which prevents dishonest or premature release claims across development workflows.