the-controller-verification-before-completion

Enforce verification commands and exit-code checks before completion claims.

13|2|Updated Mar 1, 2026

Search Tags:#code quality #testing #devops #ci/cd #verification #agile

Ready to run

npx skills add https://github.com/kwannoel/the-controller --skill the-controller-verification-before-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: the-controller-verification-before-completion
Source: https://github.com/kwannoel/the-controller/tree/main/skills/the-controller-verification-before-completion
Command: npx skills add https://github.com/kwannoel/the-controller --skill the-controller-verification-before-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of work completion, ensuring that all verification steps are performed before any assertion of success, thereby maintaining honesty and preventing costly errors.

Core Features & Use Cases

Mandatory Verification: Enforces running specific commands to validate claims about tests, linters, builds, bug fixes, or agent completions.
Evidence-Based Claims: Requires tangible output and exit codes as proof before any success statement is made.
Use Case: Before declaring a bug fixed, this Skill ensures you re-run the relevant test case and confirm it passes, rather than assuming the fix worked.

Quick Start

Always run the verification command and check its output before claiming any work is complete.

Frequently Asked Questions about the-controller-verification-before-completion

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

FAQPage Schema

How do I prevent premature task completion claims in CI/CD pipelines?▼

To prevent premature task completion claims, you must enforce a strict verification process that runs specific validation commands and analyzes their full output and exit codes before asserting success.

How do I verify code changes before committing or creating a pull request?▼

Verifying code changes before committing requires executing mandatory validation commands, such as linters or builds, and confirming tangible output as evidence to prevent premature pull request creation.

What is mandatory verification in agile development?▼

Mandatory verification in agile development is a strict process requiring demonstrable proof of work state, enforcing the execution of specific validation commands before any claims of task success or completion are made.

How to enforce evidence-based claims for bug fixes?▼

To enforce evidence-based claims for bug fixes, you must re-run the relevant test case, analyze the full output, and confirm the passing exit code as tangible proof before declaring the bug fixed.

Does this verification process require specific dependencies or testing frameworks?▼

No, this verification process does not require specific dependencies or testing frameworks. It mandates running validation commands and checking their output and exit codes, regardless of the tools used.

What is the best way to ensure agents only claim success after demonstrable proof?▼

The best way to ensure agents claim success only after demonstrable proof is to enforce a strict verification process requiring execution of validation commands and confirmation of evidence before any assertion of status.