skills.rest
AlejandroFigini
AlejandroFiginiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Require fresh verification evidence before accepting task completion claims.

Updated Mar 27, 2026
Search Tags:#validation#verification#quality-assurance#code-review#continuous-integration#process-governance#test-outputs
One-click install
npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill verification-before-completion-alejandrofigini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/AlejandroFigini/artist-portfolio/tree/main/.agent/skills/verification-before-completion
Command: npx skills add https://github.com/AlejandroFigini/artist-portfolio --skill verification-before-completion-alejandrofigini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that completion claims are backed by fresh verification evidence, preventing premature success declarations.

Core Features & Use Cases

  • Gate completion by running verification commands and validating their outputs.
  • Capture and reference evidence (logs, test results, artefacts) as proof of completion.
  • Apply to software development workflows, code reviews, PRs, builds, and deployments requiring validation gates.

Quick Start

Run the full verification command suite and report the results before making any success claims.

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 continuous integration workflows?▼

To prevent premature completion claims in continuous integration, gate task completion by running verification commands to completion and analyzing their outputs for success criteria before making any success claims.

What is verification evidence in software development and when do I need it?▼

Verification evidence in software development is fresh logs, test results, and artifacts captured as proof of completion. You need it whenever validation gates determine completion in builds, deployments, or code reviews.

How do I gate code reviews and pull requests with fresh test outputs?▼

Gate code reviews and pull requests by running the full verification command suite, capturing test outputs as evidence, and requiring verifiable results before allowing any success declarations.

Does process governance for deployments require validation gates before completion?▼

Yes, process governance for deployments requires validation gates before completion. You must run verification commands, analyze outputs for success criteria, and reference evidence as proof before claiming deployment success.

What's the best way to validate test outputs before declaring a build successful?▼

The best way to validate test outputs before declaring a build successful is to run verification commands to completion, analyze outputs against success criteria, and make claims only with verifiable results as evidence.

Related Skills

Explore More Software Engineering Skills→
apexbusiness-systemsapexbusiness-systems
4

verification-before-completion

Run fresh verification commands and report evidence before completion claims.

Community
Basic
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
djimitdjimit
1

execute

Automate code execution across AI agents with QA gates and evidence logs.

Community
Advanced