skills.rest
qdzsh
qdzshCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verify-before-complete

Run the project's verification command and quote fresh output as evidence.

12|1|Updated May 29, 2026
Search Tags:#workflow#verification#evidence#tests#gsd#completion-claims
One-click install
npx skills add https://github.com/qdzsh/gsd-revamp --skill verify-before-complete
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-before-complete
Source: https://github.com/qdzsh/gsd-revamp/tree/main/src/resources/skills/verify-before-complete
Command: npx skills add https://github.com/qdzsh/gsd-revamp --skill verify-before-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that completion claims are not made without fresh verification evidence produced in the current message, preventing risky or unfounded statements about progress, builds, tests, or tasks.

Core Features & Use Cases

  • Enforces "evidence before claims" as a hard gate for task completion and signaling milestones, commits, and pull requests.
  • Provides a step-by-step verification workflow mapping claims to verifications and requiring fresh output after code changes.
  • Applicable across slice boundaries, task finishing, and user-facing answers to ensure integrity of reported progress.

Quick Start

Run the verification workflow after each change and quote the fresh tool output in your completion claim.

Frequently Asked Questions about verify-before-complete

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

FAQPage Schema
How do I ensure tests pass before claiming a task is complete?▼

Gate completion claims by identifying the exact milestone, running the project's verification command after the last code change, and quoting the fresh tool output as evidence before signaling task completion.

What is evidence-based verification for workflow completion claims?▼

Evidence-based verification is a workflow mechanism that maps exact completion claims to verification commands, requiring fresh tool output as proof within the current message to prevent unfounded statements about progress, builds, or tests.

How to prevent unfounded build or test progress claims in software engineering?▼

Prevent unfounded progress claims by enforcing a hard gate that requires invoking the project's verification command after code changes and embedding the fresh output as quoted evidence before making any user-facing completion statements.

Do I need specific test frameworks to gate completion with fresh verification?▼

No specific test frameworks are required. You map your existing project's verification command to the completion claim you are about to make, ensuring the command runs after the last code change to produce fresh evidence.

When should I run a verification workflow for task completion claims?▼

Run the verification workflow after each code change and before signaling milestones, commits, pull requests, or user-facing answers, ensuring the verification output is fresh and mapped directly to the specific completion claim.

Related Skills

Explore More Software Engineering Skills→
lie5860lie5860
30

verification-before-completion

Require verification evidence before declaring task completion in development workflows.

Community
Advanced
BlackRoad-OS-IncBlackRoad-OS-Inc
1

verification-before-completion

Runs verification commands and reports their outputs before declaring completion.

Official
Intermediate
hugo-berendihugo-berendi
3

verification-before-completion

Run verification commands and attach output evidence before task completion.

Community
Basic
fredrikaverpilfredrikaverpil
253

code-review

Enforce evidence-based verification gates before claiming code review completion.

Community
Basic