verification-before-completion

Require verifiable evidence before marking work complete in code reviews.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/dmulcahey/featureforge --skill verification-before-completion-dmulcahey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/dmulcahey/featureforge/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/dmulcahey/featureforge --skill verification-before-completion-dmulcahey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents premature completion claims by requiring verifiable evidence before marking work as done.

Core Features & Use Cases

  • Enforces verification commands and evidence gathering before assertions.
  • Gating of PR approvals and merges to ensure outputs align with verified results.
  • Use case: QA gates and review workflows that require auditable checks and traceable artifacts.

Quick Start

Run the verification workflow and attach its results to your 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 prevent premature completion claims in automated PR workflows?

Prevent premature completion claims by enforcing verifiable evidence gathering before marking work as done. This gating mechanism requires running verification commands and attaching traceable artifacts to PR approvals, ensuring outputs match verified results across branches.

What is verification gating in code review and QA workflows?

Verification gating is a mechanism that prevents marking work as done until verifiable evidence is attached. It enforces explicit verification steps, citation of checks, and traceable artifacts during code reviews and QA gates to ensure outputs match verified results.

How do I require verifiable evidence before approving pull requests across branches?

Require verifiable evidence before PR approvals by gating merges on explicit verification commands and traceable artifacts. This automated workflow ensures completion claims are backed by verified results, aligning outputs across different branches and contributors.

Does verification gating work with existing automated PR workflows?

Verification gating works with existing automated PR workflows by applying during code reviews, QA gates, and PR approvals. It requires no dependencies and integrates into your current process by enforcing evidence gathering and citation of checks.

Why does my automated workflow allow claiming completion without traceable artifacts?

Automated workflows allow premature completion when lacking explicit verification gating. By requiring traceable artifacts and citation of checks before marking work as done, you ensure outputs match verified results and prevent unverified claims across contributors.