verification-before-completion

Enforce a five-step verification gate before claiming software work complete.

20|4|Updated Feb 2, 2026

Search Tags:#verification #audit #evidence #ci-cd #claims #gate

Ready to run

npx skills add https://github.com/Alenryuichi/openmemory-plus --skill verification-before-completion-alenryuichi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Alenryuichi/openmemory-plus/tree/main/.augment/skills/verification-before-completion
Command: npx skills add https://github.com/Alenryuichi/openmemory-plus --skill verification-before-completion-alenryuichi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Declaring software completion without verification risks inaccuracies and erodes trust; this skill enforces a gate that requires fresh evidence before any success claim.

Core Features & Use Cases

Enforces a five-step gate: IDENTIFY, RUN, READ, VERIFY, and ONLY THEN CLAIM.
Applies during software development, CI/CD, code reviews, and PR approvals to ensure verification is performed before status updates.
Provides an auditable trail of verification outcomes for accountability and compliance.

Quick Start

Run the verification workflow and claim completion only when the output confirms success.

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 declaring code completion without verification evidence?▼

To prevent declaring code completion without verification evidence, you can enforce a five-step gate that requires running tests and reading fresh output before approving PRs or status updates.

What is the best way to enforce a verification gate during CI/CD and code reviews?▼

The best way to enforce a verification gate during CI/CD and code reviews is to require explicit IDENTIFY, RUN, READ, and VERIFY steps, blocking any success claim until fresh evidence is recorded.

How does requiring fresh verification evidence improve software development audit trails?▼

Requiring fresh verification evidence improves software development audit trails by recording explicit outcomes at each step, ensuring accountability and compliance before any work is marked complete.

Can I use a verification gate to block dishonest completion claims in PR approvals?▼

Yes, you can use a verification gate to block dishonest completion claims in PR approvals by mandating that developers perform and document fresh verification before updating task statuses.

What are the limitations of enforcing a manual verification gate before claiming completion?▼

A limitation of enforcing a manual verification gate before claiming completion is that developers must strictly follow the five-step process; skipping the READ or VERIFY steps undermines the audit trail and risks inaccurate status updates.