verification-before-completion

Standardizes a verification process for work completion claims in software development.

8|1|Updated Feb 25, 2022

Search Tags:#verification #completion claims #rework prevention #work integrity #honesty in work

Ready to run

npx skills add https://github.com/ayubun/dotfiles --skill verification-before-completion-ayubun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ayubun/dotfiles/tree/main/configs/opencode/skills/ed3d-plan-and-execute/verification-before-completion
Command: npx skills add https://github.com/ayubun/dotfiles --skill verification-before-completion-ayubun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a framework for ensuring that claims of work completion are backed by verifiable evidence, preventing dishonesty and rework.

Core Features & Use Cases

Evidence-Driven Claims: Ensures that claims of success are based on concrete verification results.
Standardized Verification Process: Defines a clear set of steps to verify work before making any success claims.
Preventative Rework: Aids in catching potential issues early, reducing rework and time wastage.

Quick Start

Run the verification steps before committing or creating PRs, using the outlined process in the skill documentation.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I verify work completion before claiming a bug fix is done?▼

To verify work completion before claiming a bug fix is done, apply a standardized verification process requiring concrete evidence of success. This prevents dishonesty and reduces rework by catching potential issues early.

What is the best way to prevent rework during feature development?▼

The best way to prevent rework during feature development is enforcing evidence-driven completion claims through a standardized verification process. This ensures all success claims are backed by verifiable results, maintaining work integrity.

How do I standardize the code review verification process?▼

Standardize the code review verification process by running defined verification steps before committing or creating pull requests. This disciplined approach ensures claims of work completion are consistently supported by verifiable evidence.

Do I need external dependencies to ensure honesty in software development workflows?▼

No, you do not need external dependencies to ensure honesty in software development workflows. This verification process operates independently, applying a disciplined approach to validate completion claims across code review and feature development.

When should I apply completion verification in software development?▼

Apply completion verification in software development across all stages of work, including code review, bug fixes, and feature development. Run the verification steps before committing or creating pull requests to ensure work integrity.