acceptance-verification

Verify delivered functionality against acceptance criteria and generate VERIFICATION.md artifacts.

9|1|Updated Feb 1, 2026

Search Tags:#documentation #qa #verification #criteria #acceptance #uat

Ready to run

npx skills add https://github.com/calcosmic/Aether --skill acceptance-verification-calcosmic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-verification
Source: https://github.com/calcosmic/Aether/tree/main/.aether/skills-codex/colony/acceptance-verification
Command: npx skills add https://github.com/calcosmic/Aether --skill acceptance-verification-calcosmic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delays and ambiguity in phase progress by lacking a structured method to validate delivered functionality against formal acceptance criteria.

Core Features & Use Cases

Guided, interactive verification of each acceptance criterion.
Auto-generation of a VERIFICATION.md artifact with evidence for each criterion.
Blocks or flags when verification cannot proceed until issues are resolved.

Quick Start

Identify acceptance criteria from the phase documents and walk through each criterion to determine PASS/FAIL and generate the VERIFICATION.md artifact.

Frequently Asked Questions about acceptance-verification

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

FAQPage Schema

How do I verify delivered features against acceptance criteria before phase progress?▼

To verify delivered features, you need structured acceptance criteria validation. This Skill guides interactive verification of each criterion, records PASS/FAIL outcomes, and generates a VERIFICATION.md artifact to remove ambiguity before advancing project phases.

What is the best way to document UAT outcomes for project phases?▼

The best way to document UAT outcomes is generating a VERIFICATION.md artifact. This Skill records pass/fail results and auto-diagnoses issues during interactive verification, ensuring formal criteria validation and evidence-based documentation for phase progress.

How does interactive acceptance verification handle failing criteria?▼

Interactive acceptance verification blocks or flags progress when criteria fail. The Skill auto-diagnoses issues during UAT, recording PASS/FAIL status in the VERIFICATION.md artifact, ensuring phase progress halts until resolution.

Do I need formal acceptance criteria defined to use automated UAT verification?▼

Yes, you need formal acceptance criteria defined in phase documents. The Skill extracts these criteria to walk through interactive verification, validating delivered functionality and generating the VERIFICATION.md artifact with evidence.

When do I need to generate a VERIFICATION.md artifact for delivered functionality?▼

You need a VERIFICATION.md artifact when phase progress requires formal UAT and criteria validation. It documents interactive verification outcomes, ensuring delivered features meet defined acceptance criteria before moving forward.

Can I use acceptance verification for colony workflows requiring formal criteria validation?▼

Yes, acceptance verification applies to colony workflows and project phases. It ensures interactive verification, pass/fail recording, auto-diagnosis, and VERIFICATION.md artifact generation for formal UAT and criteria validation.