uat-workflows

Automate UAT workflow validation by verifying acceptance criteria and logging structured bug reports.

Updated Mar 5, 2026

Search Tags:#workflow #testing #permissions #acceptance-criteria #ticketing #bug-report #uat

Ready to run

npx skills add https://github.com/johwer/marketplace --skill uat-workflows

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: uat-workflows
Source: https://github.com/johwer/marketplace/tree/main/skills/uat-workflows
Command: npx skills add https://github.com/johwer/marketplace --skill uat-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UAT teams struggle to consistently validate acceptance criteria, document findings, and verify permission boundaries across complex software systems. This skill provides a repeatable workflow to systematically exercise features, capture bugs with structured reports, and ensure stakeholder sign-off.

Core Features & Use Cases

Acceptance criteria validation across tickets
Structured bug report templates for reproducible issues
Permission testing matrix and role-based checks
End-to-end UAT sign-off workflow and audit trail
Cross-browser and cross-device considerations for UI changes

Quick Start

Run a sample UAT ticket through the defined workflow to observe acceptance criteria verification and sign-off generation.

Frequently Asked Questions about uat-workflows

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

FAQPage Schema

How do I validate acceptance criteria across multiple UAT tickets?▼

To validate acceptance criteria across UAT tickets, you can run an automated workflow that systematically verifies each ticket's conditions, logs structured bug reports for failures, and enforces cross-role permission checks.

What is the best way to log structured bug reports during user acceptance testing?▼

The best way to log structured bug reports during user acceptance testing is to use a standardized template that captures reproducible issue details, ensuring clear documentation and robust failure handling for audit-ready sign-off.

How do I enforce role-based permission checks during a UAT workflow?▼

You can enforce role-based permission checks during a UAT workflow by applying a permission testing matrix that validates cross-role boundaries across different environments, ensuring stakeholders only access authorized features.

Can I use automated UAT workflows for ticket-based software repositories?▼

Yes, you can use automated UAT workflows for ticket-based software repositories to exercise happy-path and edge cases, handle deterministic execution, and generate audit-ready sign-off artifacts.

Does UAT workflow validation include cross-browser and cross-device considerations?▼

Yes, UAT workflow validation includes cross-browser and cross-device considerations to systematically exercise UI changes, ensuring features perform correctly across different environments before stakeholder sign-off.

When should I not use an automated UAT sign-off workflow?▼

You should not use an automated UAT sign-off workflow when your project lacks explicit input expectations, defined acceptance criteria, or structured ticketing, as the workflow relies on deterministic execution and robust failure handling.