verification-before-completion

Enforce a five-step verification protocol before claiming task completion.

Updated Feb 25, 2026

Search Tags:#testing #quality assurance #validation #verification #completion #reporting

Ready to run

npx skills add https://github.com/LayerDynamics/Lore --skill verification-before-completion-layerdynamics

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/LayerDynamics/Lore/tree/main/lore/skills/verification-before-completion
Command: npx skills add https://github.com/LayerDynamics/Lore --skill verification-before-completion-layerdynamics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature claims of task completion, bug fixes, or passing tests by enforcing a strict verification process before any success statement is made.

Core Features & Use Cases

Mandatory Verification: Ensures that all claims of completion, success, or passing are backed by fresh, direct evidence from executed commands.
Evidence-Based Reporting: Promotes accurate status reporting by requiring the execution and reading of verification commands (e.g., test runners, linters, build tools).
Use Case: Before reporting that a bug is fixed, this skill ensures the relevant test command is run, its output is read, and the output confirms the fix, preventing false positives.

Quick Start

Use the verification-before-completion skill to ensure all tests pass before claiming the feature is complete.

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 test verification before claiming a bug fix is complete?▼

To enforce test verification before claiming completion, apply a strict five-step protocol: Identify, Run, Read, Confirm, and Claim. This ensures all success statements are backed by fresh evidence from executed commands like test runners.

What is the best way to prevent false positives when reporting task completion?▼

The best way to prevent false positives in task completion reporting is to require evidence-based validation. You must execute relevant verification commands, read their output, and confirm the results before making any success claims.

How do I validate command output before reporting a task as passing?▼

To validate command output before reporting a task as passing, run the relevant build or test commands, read the output, and confirm it meets specific criteria. Only then can you claim the task is passing.

Does mandatory verification require running specific testing tools?▼

Mandatory verification requires running relevant validation commands such as test runners, linters, or build tools. You must execute these tools, read their output, and confirm the results before claiming any work is complete.

What steps should I follow to verify a bug fix before claiming success?▼

To verify a bug fix before claiming success, follow a five-step process: Identify the verification command, Run it, Read the output, Confirm the fix is validated, and then Claim completion with the evidence backing your statement.

Why does claiming task completion prematurely cause reporting issues?▼

Claiming task completion prematurely causes reporting issues because it promotes false positives. Without strict verification through executed commands and output analysis, success statements lack the fresh, direct evidence needed for accurate status reporting.