skills.rest
steven-3
steven-3COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Require verification command output as evidence before task completion.

Updated Mar 17, 2026
Search Tags:#debugging#verification#quality gates#tests#command output#completion report
One-click install
npx skills add https://github.com/steven-3/supermind --skill verification-before-completion-steven-3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/steven-3/supermind/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/steven-3/supermind --skill verification-before-completion-steven-3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents incomplete or unverified task handoffs by forcing executors to demonstrate that the work actually succeeded using real command output evidence.

Core Features & Use Cases

  • Verification-first completion contract: Requires a filled completion report for every executor, ensuring no work ends without evidence.
  • Evidence-based acceptance criteria: Treats test pass results, compiler/linter output, and working behavior outputs as valid proof.
  • Clear “no evidence” rejection rules: Blocks completion reports that lack pasted verification output, even if the work looks correct.

Quick Start

Ask your executor to complete the task only after running verification commands and pasting the resulting command output into the completion report.

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 completion before declaring a coding task finished?▼

Evidence-based completion requires executors to run verification commands and paste their stdout or stderr output into a standardized completion report before a task is considered finished.

What counts as valid verification output for a completion report?▼

Valid verification output includes passing test results, compiler or linter output, and working behavior outputs pasted directly into the completion report to prove the task succeeded.

How do I stop incomplete tasks from being handed off without running tests?▼

You can block incomplete handoffs by applying a verification-first completion contract that rejects any completion report lacking pasted command output, even if the work appears correct.

Can I use this verification gate for debugging and refactoring workflows?▼

Yes, this verification gate applies directly to executor-driven coding, debugging, refactoring, and feature delivery workflows where success must be demonstrated with real command output.

Why does my task completion report get rejected when the code looks correct?▼

Completion reports are rejected when they lack pasted verification command output, because the system enforces a strict no-evidence rejection rule regardless of how correct the work appears.

What is a verification-first completion contract?▼

A verification-first completion contract is a rule requiring a fully filled completion report with pasted command output evidence for every executor, ensuring no work ends without proof.

Related Skills

Explore More Software Engineering Skills→
motoki317motoki317
4

Investigation Patterns

Generate evidence-based reports through a phased workflow for codebase investigation.

Community
Advanced
truongnattruongnat
1

cli-pro

Design and standardize CLI interfaces with subcommands, flags, and shell completion.

Community
Advanced
flight505flight505
9

Plugin Guide & Help

Guide users through Storybook Assistant Plugin features and commands.

Community
Basic
BubbleBufferBubbleBuffer
3

verification-before-completion

Run verification commands fully before reporting task completion with evidence outputs.

Community
Advanced