skills.rest
moberghr
moberghrOFFICIAL
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Require fresh execution evidence before reporting software tasks complete.

6|Updated Mar 30, 2026
Search Tags:#workflow#qa#verification#completion#evidence#command
One-click install
npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill verification-before-completion-moberghr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/moberghr/mtk-agent-toolkit/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/moberghr/mtk-agent-toolkit --skill verification-before-completion-moberghr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Require fresh execution evidence before claiming a task is complete, ensuring verifiable outcomes and auditable state.

Core Features & Use Cases

  • Enforces verification commands before closing tasks, handoffs, or releases.
  • Captures exit codes and outputs to support auditable claims.
  • Guards against stale or speculative completion in software workflows.

Quick Start

Run the verification command to obtain fresh evidence and report results with the full command output.

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 fresh verification before reporting a software task as complete?▼

Fresh verification requires running a defined command after your latest code change to capture full output and exit status, preventing premature completion claims by validating execution evidence before any task handoff or closure.

What is stale completion in QA workflows and how does execution evidence prevent it?▼

Stale completion occurs when a task is reported done based on outdated or speculative results rather than fresh execution evidence. Capturing command output and exit status after the latest code change guards against this by enforcing verifiable outcomes.

How do I capture exit codes and command output for auditable task completion?▼

To capture exit codes and command output for auditable task completion, run your defined verification command, collect the full output and exit status, and validate that this evidence is fresh after your most recent code change.

Does this verification process work with bug fixes, builds, and test runs?▼

Yes, this verification process applies to bug fixes, builds, tests, and QA verifications across software development workflows by requiring fresh execution evidence and exit status validation before closing any task or handoff.

What's the best way to prevent speculative completion claims in software development?▼

The best way to prevent speculative completion claims is to enforce a verification command that captures fresh execution evidence, full output, and exit status after the latest code change, ensuring all completion reports are verifiable and auditable.

When do I need to run a verification command for task handoffs?▼

You need to run a verification command for task handoffs whenever you intend to report a task as complete, ensuring you collect fresh execution evidence and validate the output after the latest code change before any release or closure.

Related Skills

Explore More Software Engineering Skills→
growingiogrowingio
91

verification-before-completion

Run automated test commands and analyze output logs to validate code changes.

Official
Intermediate
manatagomanatago

kiro-verify-completion

Verifies task, fix, test, and feature claims using fresh command outputs and exit codes.

Community
Advanced
zerAdazerAda

bmad-qa-generate-e2e-tests

Generate end-to-end API and UI tests for identified application features.

Community
Advanced
mikeyobrienmikeyobrien

verification-before-completion

Execute proving commands anew and inspect outputs before asserting completion with evidence.

Community
Basic