user-acceptance

Automate end-to-end user acceptance testing with structured walkthroughs and GO/NO-GO decisions.

2|Updated Feb 18, 2026

Search Tags:#sign-off #demo #walkthrough #pr-workflow #acceptance-testing #uat #user-acceptance

Ready to run

npx skills add https://github.com/gannonh/skills --skill user-acceptance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: user-acceptance
Source: https://github.com/gannonh/skills/tree/main/user-acceptance
Command: npx skills add https://github.com/gannonh/skills --skill user-acceptance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Acceptance at delivery time should be experiential, not just CI results. This guide helps humans directly observe and verify delivered behavior through a structured UAT walkthrough.

Core Features & Use Cases

Structured acceptance walkthroughs with interactive demonstrations and proof of impact
Clear output contract including pass/fail slices and a final GO/NO-GO decision
Playbooks for user-facing, non-user-facing, and mixed scenarios to guide validation

Quick Start

Follow the walkthrough to perform a live acceptance demo and capture acceptance proof.

Frequently Asked Questions about user-acceptance

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

FAQPage Schema

How do I structure user acceptance testing for a PR sign-off?▼

User acceptance testing for PR sign-off is structured through interactive walkthroughs and executable demonstrations that validate behavior before merging. This approach provides a reproducible acceptance plan with clear pass/fail slices.

What is the best way to perform a UAT walkthrough for non-user-facing changes?▼

A UAT walkthrough for non-user-facing changes uses specific playbooks to guide validation and capture proof of impact. This ensures experiential verification rather than relying solely on CI results for ticket sign-off.

How do I standardize end-to-end acceptance testing across different ticket scenarios?▼

Standardize end-to-end acceptance testing by applying structured playbooks for user-facing, non-user-facing, and mixed scenarios. The workflow outputs a final GO/NO-GO decision based on captured acceptance proof.

Can I automate user acceptance demonstrations for pull request workflows?▼

Yes, you can automate user acceptance demonstrations within pull request workflows. The system applies a defined output contract and clear guardrails to validate behavior and generate reproducible acceptance plans.

Why do I need a structured acceptance plan instead of just checking CI results before merging?▼

A structured acceptance plan is needed because delivery time acceptance should be experiential, allowing humans to directly observe behavior. Relying only on CI results misses the interactive verification required for confident sign-off.

Does user acceptance testing work for mixed scenarios involving both user and non-user-facing changes?▼

User acceptance testing supports mixed scenarios through dedicated playbooks that guide validation for both user and non-user-facing changes. This ensures all delivered behavior is verified through interactive demonstrations.