verification-before-completion

Enforce a verification gate before marking work complete.

Updated Nov 8, 2024
One-click install
npx skills add https://github.com/cqkxxc/cqkxxc.github.io --skill verification-before-completion-cqkxxc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/cqkxxc/cqkxxc.github.io/tree/main/.trae/skills/verification-before-completion
Command: npx skills add https://github.com/cqkxxc/cqkxxc.github.io --skill verification-before-completion-cqkxxc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminate premature completion claims by requiring fresh verification evidence before asserting success.

Core Features & Use Cases

  • Enforces a formal verification gate before status changes (e.g., PRs, deployments).
  • Guides users through a deterministic 5-step process to verify results.
  • Captures and references verifiable outputs as evidence for audits and reviews.

Quick Start

Run the full verification command for your project, review the output with its exit status, and only claim completion if the results contain fresh, verifiable evidence.

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 a task is complete?

To enforce verification before claiming completion, apply a formal gating process requiring fresh verification evidence prior to marking work as done.

What is a verification gate in software development workflows?

A verification gate in software development is a quality-assurance checkpoint that prevents status changes like pull request merges or deployments until fresh, verifiable evidence confirms the work is complete.

How do I stop premature completion claims on pull requests and deployments?

Stop premature completion claims by capturing and referencing verifiable outputs as evidence, ensuring a deterministic step-by-step process is followed to identify, run, and read test results before success is asserted.

Does this verification workflow require specific test frameworks or dependencies?

No specific test frameworks or dependencies are required. The verification workflow applies to any project that can run a full verification command and review its exit status.

What's the best way to capture verification evidence for project audits?

The best way to capture verification evidence for audits is to run your project's full verification command, review the output and exit status, and reference those fresh verifiable results as proof of completion.