verification-before-completion

Enforce verification commands and review output before claiming work completion.

Updated Apr 23, 2026

Search Tags:#software development #verification #honesty #process enforcement #work completion

Ready to run

npx skills add https://github.com/MudraMartin/dotlight-skillset --skill verification-before-completion-mudramartin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/MudraMartin/dotlight-skillset/tree/main/superpowers/verification-before-completion
Command: npx skills add https://github.com/MudraMartin/dotlight-skillset --skill verification-before-completion-mudramartin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent dishonesty by requiring verification before claiming work is complete, fixed, or passing.

Core Features & Use Cases

Verification Commands: Ensures that specific commands are run and output is reviewed before making claims.
Evidence-Based Claims: Encourages honesty by requiring evidence before making success claims.
Preventing False Claims: Helps avoid false completions and reworks by enforcing verification steps.

Quick Start

Run the verification command before claiming any work is complete or passing.

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 verification commands before claiming work completion in software development?▼

Enforcing verification commands requires running specific tests and reviewing their output before making any success claims. This process ensures evidence-based accuracy and prevents false completions by requiring proof of work before finalizing.

What is the best way to prevent false claims of work being fixed or passing?▼

Preventing false claims involves implementing evidence-based verification steps that mandate running validation commands. This enforces honesty in software workflows by requiring developers to review actual command output before claiming a task is complete.

How do I require evidence for software development completion claims?▼

Requiring evidence for completion claims involves enforcing the execution of verification commands and checking their output. This mechanism prevents dishonesty by ensuring that all success claims are backed by concrete data.

Does process enforcement for work completion apply to any software development workflow?▼

Process enforcement for work completion applies broadly to software development workflows to ensure honesty and accuracy. It functions by requiring verification commands to run and their output to be reviewed before any completion claims are made.

Why should I run verification commands before claiming a software task is complete?▼

Running verification commands before claiming completion prevents false claims and avoids unnecessary reworks. It enforces honesty by requiring you to review the actual output and back your success claims with evidence.

What are the limitations of enforcing verification before completion?▼

Enforcing verification before completion relies on the accurate execution and review of verification commands. It does not automatically fix issues but requires manual output checking to ensure work completion claims are honest and evidence-based.