skills.rest
reynalivan
reynalivanCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforce a four-step verification flow before marking tasks complete.

Updated Feb 15, 2026
Search Tags:#qa#verification#audit#completion#governance#evidence#process
One-click install
npx skills add https://github.com/reynalivan/EMMM2 --skill verification-before-completion-reynalivan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/reynalivan/EMMM2/tree/main/.agent/skills/verification-before-completion
Command: npx skills add https://github.com/reynalivan/EMMM2 --skill verification-before-completion-reynalivan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents completion claims from being made without fresh verification evidence.

Core Features & Use Cases

  • Enforces evidence-based completion by requiring explicit verification steps before closing tasks or merging PRs.
  • Provides a standardized gate function (IDENTIFY, RUN, READ, VERIFY) to ensure output is accurate and auditable.
  • Reduces risk of misrepresentation and rework by making verification artifacts mandatory for claims in development workflows.

Quick Start

Run the full verification command and attach its output as evidence before marking the task complete.

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 task completion claims without fresh verification evidence in software development?▼

To prevent completion claims without verification evidence, enforce a standardized four-step gate flow that requires running tests and attaching auditable artifacts before closing tasks or merging pull requests.

What is evidence-based completion in QA and project handoffs?▼

Evidence-based completion is a governance process that mandates running explicit verification steps and producing auditable outputs to support audit-ready task closure, reducing the risk of misrepresentation and rework.

How do I enforce a verification flow before merging pull requests?▼

You can enforce a verification flow before merging pull requests by applying a four-step process—IDENTIFY, RUN, READ, VERIFY—to generate mandatory verification artifacts that support audit-ready completion.

Does this verification process work for project handoffs requiring audit-ready completion?▼

Yes, this verification process works for project handoffs by enforcing an evidence-based completion gate that produces standardized, auditable outputs to support governance and audit requirements.

Why do I need to run a verification gate before marking a task complete?▼

You need to run a verification gate before marking a task complete to ensure output accuracy, make verification artifacts mandatory, and significantly reduce the risk of misrepresentation and subsequent rework.

Related Skills

Explore More Software Engineering Skills→
arthrodarthrod

conejo-merge

Implement pull request comments with gate-based verification and test-first development.

Community
Advanced
kucherenkokucherenko
71

sweep-verification

Enforce fresh verification evidence before declaring artifact completion.

Community
Advanced
haidonglethqbhaidonglethqb

test

Automate unit, integration, end-to-end, and UI test orchestration with coverage reporting.

Community
Intermediate
kevinnguyen271090kevinnguyen271090
15

code-review

Enforce code-review governance with verification gates before completion claims.

Community
Basic