skills.rest
beyondwen
beyondwenCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Gate completion claims with evidence-based validation workflows.

Updated Mar 30, 2026
Search Tags:#workflow#validation#verification#evidence#quality-assurance#pull-request
One-click install
npx skills add https://github.com/beyondwen/track-record-new --skill verification-before-completion-beyondwen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/beyondwen/track-record-new/tree/main/.gemini/skills/verification-before-completion
Command: npx skills add https://github.com/beyondwen/track-record-new --skill verification-before-completion-beyondwen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This rule enforces that no completion statements are made without verifiable evidence, promoting honesty and efficiency by requiring tests and outputs to support claims of completion.

Core Features & Use Cases

  • Gate all completion claims with evidence-based validation to ensure traceable decisions.
  • Follow a clear 5-step process: determine, run, read, validate, and conclude, to guarantee reproducible outcomes.
  • Use in pull requests, task closures, and release handoffs to prevent premature declarations and reduce rework.

Quick Start

Run the verification workflow before marking any task 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 validation before declaring a task complete?▼

A 5-step gating workflow determines requirements, runs verification commands, reads outputs, validates evidence, and concludes status. This process guarantees reproducible outcomes before allowing any completion statements.

What is the best way to prevent premature declarations in pull requests?▼

Preventing premature declarations in pull requests requires a gating workflow that validates evidence before status claims. This enforces traceable decisions by aggregating test outputs to support completion statements.

How does evidence-based verification work for release handoffs?▼

Evidence-based verification for release handoffs works by gating the handoff with a 5-step process: determine, run, read, validate, and conclude. It requires executing verification commands to aggregate outputs before validating the release status.

Do I need to run tests to mark a task complete with verification validation?▼

Yes, verification validation requires running tests and executing verification commands to produce outputs. No completion statements can be made without verifiable evidence aggregated from these runs.

Why does workflow validation require aggregating outputs before task closure?▼

Workflow validation requires aggregating outputs to ensure traceable decisions and reproducible outcomes during task closure. This evidence-based gating reduces rework by preventing unsupported completion claims.

Related Skills

Explore More Software Engineering Skills→
wecode-aiwecode-ai
705

sandbox

Run shell commands and manipulate files inside an isolated E2B sandbox.

Official
Advanced
liauw-medialiauw-media
3

verification-before-completion

Enforces pre-shipment verification checklists for roles, privileges, and warehouse assignments in the PlayerLifecycle domain.

Community
Basic
eroslifestyleeroslifestyle
1

verification-loop

Automate code change verification against user requests and acceptance criteria.

Community
Advanced
InnerScopeHearingInnerScopeHearing

verification-before-completion

Standardize verification workflows requiring manual command execution and output confirmation.

Official
Basic