skills.rest
mealpac
mealpacCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforces fresh verification evidence before software tasks are marked complete.

1|Updated Mar 13, 2026
Search Tags:#qa#verification#governance#evidence#ci-cd#code-review
One-click install
npx skills add https://github.com/mealpac/manus --skill verification-before-completion-mealpac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/mealpac/manus/tree/main/skills/workflow-skills/verification-before-completion
Command: npx skills add https://github.com/mealpac/manus --skill verification-before-completion-mealpac

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures honest completion claims by enforcing fresh verification evidence before any success statements.

Core Features & Use Cases

  • Enforces a verified completion workflow by requiring explicit verification steps, outputs, and evidence before any status updates.
  • Guides code reviews, PRs, and deployments to rely on verifiable results rather than assumptions.
  • Use Case: In a CI/CD pipeline, only mark a build as done after running the verification command and confirming the results.

Quick Start

Run the full verification command, review the output, and only assert success when the evidence confirms the 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 enforce fresh verification evidence before marking a CI/CD build as complete?▼

Run full verification commands, analyze outputs for failures, and only assert success when the evidence confirms the claim. This ensures fresh verification evidence before marking any CI/CD build or PR update as complete.

What is verified completion in software development workflows?▼

Verified completion is a governance process requiring explicit verification steps and outputs before any status updates. It ensures completion claims are backed by fresh verification evidence rather than assumptions.

How do I ensure code review claims are backed by verifiable results?▼

Guide the code review process to rely on running full verification commands and analyzing the actual output. Only report success when the evidence explicitly confirms the claim.

Do I need to run full verification commands for every PR update?▼

Yes, you need to run full verification commands for every PR update. This governance approach requires analyzing the actual output for failures and reporting the actual status with evidence before asserting any success.

What is the best way to prevent false completion claims during deployments?▼

Enforce a verified completion workflow to prevent false completion claims. This requires running full verification commands, analyzing outputs for failures, and reporting actual status with evidence before any success statements.

Related Skills

Explore More Software Engineering Skills→
MINT-IAMINT-IA

verification-before-completion

Run and inspect verification commands before claiming work completion.

Official
Intermediate
JaviMontanoJaviMontano

apex-contingency-planning

Calculate contingency reserves using EMV, benchmarks, and Monte Carlo analysis.

Community
Advanced
JaiminVadadoriyaJaiminVadadoriya
1

qa-project-context

Create a QA context file capturing tech stack, test frameworks, and CI/CD details.

Community
Advanced
apexbusiness-systemsapexbusiness-systems
4

verification-before-completion

Run fresh verification commands and report evidence before completion claims.

Community
Basic