skills.rest
DecentralizedGeo
DecentralizedGeoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforce evidence-based verification before claiming task completion.

1|Updated Jan 14, 2026
Search Tags:#qa#verification#governance#evidence#code-review#claims
One-click install
npx skills add https://github.com/DecentralizedGeo/stac-manager --skill verification-before-completion-decentralizedgeo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/DecentralizedGeo/stac-manager/tree/main/.github/skills/verification-before-completion
Command: npx skills add https://github.com/DecentralizedGeo/stac-manager --skill verification-before-completion-decentralizedgeo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents unverified completion claims by enforcing evidence-based verification throughout work.

Core Features & Use Cases

  • Enforces a structured verification workflow: identify, run, read outputs, verify, and only then claim success.
  • Reduces risk of misrepresentation by requiring fresh verification evidence before PRs or releases.
  • Suitable for software development, QA, and project governance workflows that demand traceable proof.

Quick Start

Run the recommended verification commands and attach the resulting evidence before marking any task as 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 enforce evidence-based verification before claiming a task is complete?▼

Evidence-based verification requires running recommended verification commands, reviewing their outputs, and documenting the results to substantiate success claims before marking any task complete. This structured workflow prevents misrepresentation and ensures responsible releases.

What is evidence-based verification in software project governance?▼

Evidence-based verification in project governance is a workflow that demands fresh proof of success before pull requests or releases. It requires identifying, running, reading outputs, and verifying commands to ensure work claims are fully substantiated and traceable.

How do I prevent unverified completion claims in my QA workflow?▼

Prevent unverified completion claims by enforcing a structured QA workflow: identify, run verification commands, read outputs, verify results, and only then claim success. This process requires fresh evidence before pull requests or releases to reduce misrepresentation risk.

Does this verification workflow apply to software development and project governance?▼

Yes, this verification workflow applies directly to software development, QA, and project governance. It is designed for any context demanding traceable proof, ensuring success claims are substantiated through documented verification command outputs before releases.

How do I attach verification evidence before marking a release as complete?▼

Attach verification evidence by running the recommended verification commands and documenting their outputs before marking the release complete. This ensures all success claims are supported by fresh, traceable proof rather than unverified assertions.

Related Skills

Explore More Product & Management Skills→
pur3v4d3rpur3v4d3r
6

verification-before-completion

Run verification and attach fresh output before claiming completion.

Community
Advanced
FernanSuozaFernanSuoza

qa-release-readiness

Collect release evidence and assemble readiness inputs for go/no-go decisions.

Community
Advanced
compozycompozy
83

verification-before-completion

Verify work claims with fresh evidence before declaring completion.

Official
Intermediate
vtgiang-dotcomvtgiang-dotcom
3

custom-deploy-workflow

Execute stepwise deployment readiness checks for staging and production releases.

Community
Intermediate