verification

Name: verification
Availability: InStock
Author: walker

Validate code implementations against documented acceptance criteria and generate acceptance reports.

Updated Feb 19, 2026

Search Tags:#documentation #validation #qa #verification #evidence #acceptance

Ready to run

npx skills add https://github.com/walker-hzx/AI-Assistant --skill verification-walker-hzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/walker-hzx/AI-Assistant/tree/main/skills/verification
Command: npx skills add https://github.com/walker-hzx/AI-Assistant --skill verification-walker-hzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification ensures code truly satisfies the stated requirements before declaring completion, by requiring verifiable evidence from execution and planning documents.

Core Features & Use Cases

Reads plan and execution documentation to check alignment with acceptance criteria.
Generates an acceptance report that records results, evidence, and any issues.
Enforces an evidence-first policy to prevent premature claims of completion.

Quick Start

After execution logs and plan documents are ready, run the verification workflow to produce the acceptance report.

Frequently Asked Questions about verification

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

FAQPage Schema

How do I verify code implementations satisfy documented requirements before completion?▼

Code verification against requirements works by reading existing plan and execution documentation to check alignment with acceptance criteria. It enforces an evidence-first policy, ensuring claims of completion are backed by verifiable execution logs.

How do I generate an acceptance report with evidence from execution logs?▼

You generate an acceptance report by running a verification workflow after execution logs and plan documents are ready. The workflow produces an acceptance report that records validation results, supporting evidence, and any identified issues.

When do I need to use an evidence-backed validation process for software tasks?▼

Evidence-backed validation is needed for end-to-end software tasks where plans and execution logs exist. It is required when you must ensure code truly satisfies stated requirements through verifiable evidence before declaring the task complete.

Does requirement validation work without execution logs and plan documents?▼

Requirement validation does not work without execution logs and plan documents. The verification process applies specifically to end-to-end software tasks where these documents exist, as it requires them to trace execution against acceptance criteria.

What is the best way to prevent premature claims of code task completion?▼

The best way to prevent premature claims of code task completion is to enforce an evidence-first validation policy. This requires reviewing plan documents, tracing execution logs, and generating an acceptance report before declaring the task finished.