skills.rest
tomasbasso
tomasbassoCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and confirm outputs before claiming completion.

Updated Apr 25, 2026
Search Tags:#workflow#verification#completion#quality#governance#evidence#claim
One-click install
npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill verification-before-completion-tomasbasso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/tomasbasso/SistemaStockV2/tree/main/.agents/skills/verificacion-antes-de-finalizar
Command: npx skills add https://github.com/tomasbasso/SistemaStockV2 --skill verification-before-completion-tomasbasso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification risks dishonesty and delivery of potentially faulty results. This Skill ensures every success claim is backed by fresh verification.

Core Features & Use Cases

  • Enforces a structured verification step before marking tasks as done.
  • Captures and requires evidence (outputs, logs, test results) prior to PRs or handoffs.
  • Applicable to software delivery, research tasks, and project handoffs where integrity matters.

Quick Start

Run the verification process and attach fresh evidence before making any 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 enforce task verification before claiming completion in a workflow?▼

Task verification before completion requires running validation commands and capturing fresh evidence like logs or test results. This ensures outputs meet gating criteria before any success is claimed, preventing faulty deliveries.

What is the best way to capture evidence prior to project handoffs?▼

Capturing evidence prior to handoffs involves executing verification processes and attaching fresh outputs. This structured step guarantees that claims of success are backed by validated results, maintaining delivery integrity.

Why does claiming work as complete without verification risk faulty delivery?▼

Claiming completion without verification risks dishonesty because it bypasses validation. Enforcing fresh verification ensures success claims are backed by confirmed evidence, preventing the delivery of faulty results.

Can I use verification gating criteria for software development and research tasks?▼

Verification gating criteria apply to software delivery, research tasks, and project handoffs. By requiring fresh evidence and confirmed outputs, it ensures integrity across any context where success claims must be validated.

Does verification before completion require specific test outputs to meet gating criteria?▼

Verification before completion requires running verification commands and confirming outputs. These fresh test results and logs must meet established gating criteria before asserting success or finalizing any task.

Related Skills

Explore More Content & Communication Skills→
MomoDavilukeMomoDaviluke
2

verification-before-completion

Run verification commands and record evidence before declaring task completion.

Community
Advanced
xxihxxih
1

verification-before-completion

Verify command output before claiming task completion.

Community
Basic
htayjhtayj

unit-tester

Locate, execute, and interpret unit tests for code changes across testing frameworks.

Community
Intermediate
laozhong86laozhong86
1

gxpm-review-army

Orchestrate two-stage code review with spec-compliance gating and parallel quality reviewers.

Community
Advanced