skills.rest
HankLiu447
HankLiu447COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Require verification commands and evidence before any completion claim.

3|Updated Jan 18, 2026
Search Tags:#workflow#verification#completion#evidence#CI#tests
One-click install
npx skills add https://github.com/HankLiu447/SuperSpec --skill verification-before-completion-hankliu447
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/HankLiu447/SuperSpec/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/HankLiu447/SuperSpec --skill verification-before-completion-hankliu447

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures claims of task completion are backed by verifiable evidence, preventing dishonest or premature status updates and strengthening trust across teams.

Core Features & Use Cases

  • Enforces verification workflows: requires running specified verification commands and inspecting fresh outputs before asserting success.
  • Evidence-first reporting: ties completion claims to verifiable results such as test outputs, build status, or QA checks.
  • Broad applicability: suitable for software development, QA teams, and project management workflows where every task must be validated.

Quick Start

Run your project verification workflow: execute the verification command, review the full command output, confirm its exit status, and only then publish a completion claim.

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 before claiming task completion in a development workflow?▼

To enforce verification before task completion, you must execute specified verification commands, inspect the fresh command outputs, confirm the exit status, and only then publish a completion claim.

What is evidence-first reporting for software engineering tasks?▼

Evidence-first reporting ties completion claims to verifiable results like test outputs, build status, or QA checks, preventing premature status updates and ensuring claims are backed by fresh results.

Can I use verification checks for both software development and operational workflows?▼

Yes, verification checks apply to any development or operational workflow where status claims must be backed by fresh results, including software development, QA teams, and project management workflows.

How do I run a project verification workflow step by step?▼

Run a project verification workflow by executing the verification command, reviewing the full command output, confirming its exit status, and only then publishing a completion claim based on the results.

Why does requiring fresh test outputs prevent premature completion claims?▼

Requiring fresh test outputs prevents premature completion claims by forcing the interpretation of current verification results before success is asserted, ensuring no outdated or dishonest status updates are published.

Related Skills

Explore More Software Engineering Skills→
miles990miles990

verification-before-completion

Run verification commands and report results only when checks pass.

Community
Advanced
marcojsmithmarcojsmith
2

verification-before-completion

Run verification commands and validate exit codes before reporting completion.

Community
Advanced
Fandry96Fandry96
27

verification-before-completion

Run fresh verification commands and report evidence before declaring completion.

Community
Advanced
tizeetizee
2

verification-before-completion

Require fresh verification evidence before declaring code, tests, builds, or tasks complete.

Community
Advanced