openagent-verification-before-completion

Enforce approval gates before verification, completion claims, and git operations.

Updated Sep 16, 2025

Search Tags:#workflow #verification #governance #approval #software #claims #openagent

Ready to run

npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-verification-before-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openagent-verification-before-completion
Source: https://github.com/SvenMarcus/.dotfiles/tree/main/opencode/.config/opencode/skills/custom/openagent-verification-before-completion
Command: npx skills add https://github.com/SvenMarcus/.dotfiles --skill openagent-verification-before-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification before completion prevents unverified completion claims by enforcing OpenAgent-style approval gates, ensuring evidence is produced and approvals are obtained before any completion claims or git operations.

Core Features & Use Cases

Approval-gated verification: requires explicit approval before running verification commands.
Evidence-first workflow: records full command outputs and statuses before making any claims.
Gate-driven progression: blocks completion claims and commits until all gates are satisfied and approved.

Quick Start

Request approval to verify a task, run the full verification, report the evidence, and seek final approval before claiming completion.

Frequently Asked Questions about openagent-verification-before-completion

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

FAQPage Schema

How do I enforce verification gates before git commits in a software development workflow?▼

You can enforce verification gates before git commits by requiring explicit approval to run verification commands, evidence reporting, and a final approval gate before any completion claims or git operations are executed.

What is an approval-gated verification workflow and how does it prevent unverified completion claims?▼

Approval-gated verification is a workflow mechanism that blocks completion claims and commits by requiring explicit approval to run verification, producing evidence of command outputs before any success is announced.

How do I implement an evidence-first verification process for software tasks?▼

To implement evidence-first verification, request approval to run verification commands, record the full command outputs and statuses as evidence, and then seek final approval before making any completion claims or commits.

Does the OpenAgent verification process work with standard git operations and software workflows?▼

Yes, the OpenAgent verification process applies to software development workflows by enforcing approval gates before running verification commands and blocking any git operations until evidence is reported and approved.

Why do I need approval before running verification commands in a gated workflow?▼

Approval is required before running verification commands to ensure a gate-driven progression where no verification, completion claims, or commits proceed without explicit authorization and recorded evidence.

What are the limitations of using verification gates for software completion claims?▼

The verification gate approach requires explicit approval at multiple stages—before running verification and before completion claims—which may slow down workflows that do not mandate strict governance and evidence reporting.