validate-completion

Execute or inspect tasks to verify completion claims.

Updated Jul 10, 2026

Search Tags:#validation #verification #audit #software quality #task completion

Ready to run

npx skills add https://github.com/ronniepinnell/casper --skill validate-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-completion
Source: https://github.com/ronniepinnell/casper/tree/main/collection/verification-and-audit/validate-completion
Command: npx skills add https://github.com/ronniepinnell/casper --skill validate-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of unverified task completion claims, ensuring that the goals of a task or feature are genuinely achieved before they are marked as done.

Core Features & Use Cases

Single-Task Completion Verifier: Establishes whether a task or feature claim is genuinely achieved by executing it when possible or inspecting it rigorously when not.
Execution Mode: Invokes the feature for real, checks for graceful failure, and confirms expected DB state changes.
Inspection Mode: Inspects artifacts for non-empty files, no placeholders, and correct imports, with tests exercising real code paths.
Use Case: Before marking a task as done, use this Skill to ensure that the task meets all its requirements and is fully functional.

Quick Start

Run the command '/validate-completion {task_prefix}-123' to verify the completion of a task with the prefix '{task_prefix}'.

Frequently Asked Questions about validate-completion

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

FAQPage Schema

How do I verify task completion claims in software development?▼

Software task verification works by either executing the feature to confirm expected database state changes and graceful failures, or inspecting artifacts for non-empty files, correct imports, and tests exercising real code paths. This confirms completion claims are backed by actual results.

How can I validate that a software feature is actually complete before marking it done?▼

To validate a feature is complete, invoke the feature to confirm expected database state changes and graceful failure handling. Alternatively, inspect artifacts rigorously for non-empty files, absence of placeholders, correct imports, and tests exercising real code paths.

What is the difference between execution mode and inspection mode for task validation?▼

Execution mode invokes the feature for real to check for graceful failure and confirm expected database state changes. Inspection mode rigorously inspects artifacts for non-empty files, no placeholders, correct imports, and tests exercising real code paths.

Do I need execution capabilities to verify task completion claims?▼

No, execution capabilities are not strictly required. The verification process requires either execution or inspection capabilities. If execution is not possible, you can rigorously inspect artifacts for non-empty files, correct imports, and tests exercising real code paths.

What should I check for when inspecting software artifacts during task verification?▼

When inspecting software artifacts for task verification, check for non-empty files, absence of placeholders, and correct imports. Additionally, ensure that tests exercise real code paths to confirm the task or feature is fully functional.

Why should I audit task completion claims before closing a software ticket?▼

Auditing task completion claims prevents unverified features from being marked as done. By executing the feature or inspecting artifacts rigorously, you ensure the goals of a task are genuinely achieved and backed by actual results, maintaining software quality.