skills.rest
lagz0ne
lagz0neCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforce fresh verification evidence before claiming work completion.

2|1|Updated Jan 5, 2026
Search Tags:#workflow#verification#QA#evidence#software-engineering#claims
One-click install
npx skills add https://github.com/lagz0ne/prev-cli --skill verification-before-completion-lagz0ne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/lagz0ne/prev-cli/tree/main/.opencode/skill/verification-before-completion
Command: npx skills add https://github.com/lagz0ne/prev-cli --skill verification-before-completion-lagz0ne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents completion claims without verification by enforcing fresh verification evidence.

Core Features & Use Cases

  • Evidence-first validation: enforce fresh verification before claiming completion.
  • Structured workflow: identify the proving command, run it fully, read outputs, verify results, and only then communicate success.
  • Practical scenarios: applies to commits, PR reviews, and release readiness to ensure honesty and traceability.

Quick Start

Before declaring completion, run the verification steps defined in your workflow, capture full outputs, and only claim completion when the evidence supports it.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify software completion with evidence before claiming a task is done?▼

To verify software completion with evidence, you must identify the proving verification command, execute it fully, read the entire output, and confirm successful results before communicating any completion claims.

What is evidence-first validation in software engineering workflows?▼

Evidence-first validation is a software engineering workflow mechanism that enforces fresh verification before claiming completion, ensuring honesty and traceability by requiring actual command outputs to support your claims.

How do I enforce QA verification steps for pull requests and commits?▼

You enforce QA verification steps for pull requests by codifying a structured workflow that requires running verification commands, capturing full outputs, and reviewing results before declaring PR readiness or commit success.

When do I need to run fresh verification commands during development workflows?▼

You need to run fresh verification commands during development workflows whenever claiming work is complete, such as after coding, preparing commits, during PR reviews, and assessing release readiness.

What is the best way to prevent unverified completion claims in development?▼

The best way to prevent unverified completion claims is to enforce a structured software engineering workflow that mandates running proving commands and reviewing fresh output evidence before any success is communicated.

Related Skills

Explore More Software Engineering Skills→
Phife726Phife726

verification-before-completion

Execute verification commands and validate outputs before completion claims.

Community
Intermediate
aurora-atomsaurora-atoms

pr-to-release-summary

Generate structured release summaries from merged pull requests and validation evidence.

Community
Advanced
pradyumnasagarpradyumnasagar
6

agent-handoff

Automate inter-skill data transfer and provenance capture via JSON Material Passports.

Community
Advanced
tody-agenttody-agent
48

cm-quality-gate

Enforce test gates and evidence-based verification before deployment in CI/CD workflows.

Community
Advanced