aidlc-verification-before-completion

Execute verification commands and review outputs before asserting task completion.

2|Updated Mar 10, 2026

Search Tags:#workflow #testing #quality assurance #bug fixing #verification #completion

Ready to run

npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-verification-before-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aidlc-verification-before-completion
Source: https://github.com/bluejayA/devflow-aidlc-like/tree/main/skills/aidlc-verification-before-completion
Command: npx skills add https://github.com/bluejayA/devflow-aidlc-like --skill aidlc-verification-before-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents the premature declaration of task completion by enforcing a strict "no completion claims without fresh verification evidence" policy, ensuring that assertions of success are always backed by actual, up-to-date execution results.

Core Features & Use Cases

Prevents Premature Declarations: Stops agents from claiming tasks are done based on assumptions, past results, or code reviews alone.
Enforces Fresh Evidence: Mandates the execution of relevant verification commands at the moment of assertion.
Use Case: Before an agent states "The bug is fixed" or "Tests are passing," this Skill triggers a process to re-run the relevant tests and verify the output, ensuring the claim is accurate and based on current code state.

Quick Start

Use the aidlc-verification-before-completion skill to ensure all tests pass before declaring a fix is complete.

Frequently Asked Questions about aidlc-verification-before-completion

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

FAQPage Schema

How do I stop my AI agent from claiming a task is complete without running tests?▼

To prevent premature completion declarations, enforce a strict verification protocol that mandates executing relevant commands to gather fresh success evidence before any assertion is made. This ensures claims rely on current execution results rather than assumptions.

What is the verification gate process for bug fixes and task completion?▼

The verification gate process involves identifying relevant commands, executing them, reviewing the output, and validating the assertion. For bug fixes specifically, it mandates running regression testing to ensure the fix is effective.

Why do I need to re-run verification commands before declaring a bug fix is complete?▼

You need to re-run verification commands to enforce fresh evidence of success. This prevents claims based on outdated information or past code reviews, ensuring the assertion accurately reflects the current code state.

How to verify tests are passing at the moment of task completion assertion?▼

To verify tests are passing at the moment of assertion, trigger a gate process that re-runs the relevant tests and reviews the output. This validates that the completion claim is backed by actual, up-to-date execution results.

Can I use code review alone as verification evidence for task completion?▼

No, code review alone is not sufficient verification evidence. The protocol mandates the execution of relevant verification commands at the moment of assertion to prevent premature declarations based solely on assumptions or past results.