verification-before-completion

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

Enforce evidence-based verification before reporting task completion.

2|Updated Feb 25, 2026

Search Tags:#verification #evidence #process #software-engineering #claims #quality-gates

Ready to run

npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill verification-before-completion-ahmedelhadarey

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonest, not efficient.

Core Features & Use Cases

Enforces a strict, evidence-based completion process across teams.
Guides teams through a repeatable plan: identify, run, read, verify, and only-then claim.
Reduces risk of regressions and miscommunication by requiring fresh verification data.

Quick Start

Run the verification workflow before finalizing any completion claim to ensure evidence supports the outcome.

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 verification before claiming software task completion?▼

Evidence-based verification requires running a clearly defined verification command and checking fresh execution data before claiming completion. You enforce this by applying a strict workflow of identify, run, read, and verify before reporting task success.

What is the evidence-based completion process in software engineering?▼

The evidence-based completion process is a strict workflow preventing premature success claims by requiring fresh verification data. It guides teams to identify verification commands, run checks, read outputs, and verify results before approving any task completion claim.

How do I prevent premature completion claims during deployment workflows?▼

Prevent premature completion claims by enforcing a strict evidence-based verification process across deployment workflows. This ensures tests, checks, and outputs are fresh by requiring verifiable evidence reporting before approving any success claim.

Does evidence-based verification work across development and QA workflows?▼

Yes, evidence-based verification applies across development, QA, and deployment workflows. It ensures tests, checks, and outputs are fresh before reporting success, reducing the risk of regressions and miscommunication by requiring fresh execution data.

What is the best way to reduce regressions caused by unverified completion claims?▼

The best way to reduce regressions is to enforce a strict evidence-based completion process requiring fresh verification data. By guiding teams through a repeatable plan to run and verify checks before claiming completion, miscommunication risks are minimized.