uat-acceptance-review

Converts acceptance criteria into executable Given/When/Then UAT scenarios and test plans.

2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/FluxonLab/Skillry --skill uat-acceptance-review-fluxonlab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: uat-acceptance-review
Source: https://github.com/FluxonLab/Skillry/tree/main/plugins/testing-and-qa/skills/57-uat-acceptance-review
Command: npx skills add https://github.com/FluxonLab/Skillry --skill uat-acceptance-review-fluxonlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product tickets and acceptance criteria often arrive as vague bullet points with no testable steps, leaving stakeholders without a structured way to confirm a feature actually meets its goals before release. ## Core Features & Use Cases - UAT Scenario Generation: Transforms requirements, tickets, or user stories into precise Given/When/Then scenarios with exact data setup, observable outcomes, and blocking/non-blocking release gates. - Coverage & Traceability: Builds requirement-to-test traceability matrices, identifies coverage gaps, and flags implied criteria (notifications, audit logs, cascade deletes) that need product confirmation. - Test Data & Functional Test Design: Produces boundary-heavy, role-aware test data packs and risk-based functional test plans, including a game QA cycle workflow with smoke gates and sign-off reports. - Use Case: A feature is ready for stakeholder sign-off but has no formal UAT plan; use this Skill to produce a human-executable test plan covering every role, negative path, and async outcome. ## Quick Start Ask the agent to create a UAT acceptance plan from your feature ticket or PRD, covering all user roles, edge cases, and a pass/fail release gate.

Frequently Asked Questions about uat-acceptance-review

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

FAQPage Schema
How do I write UAT test scenarios from acceptance criteria?▼

Extract each acceptance criterion verbatim, then write Given/When/Then scenarios per user role with exact preconditions, actions, and observable outcomes. Add negative paths, permission boundaries, and a blocking/non-blocking pass/fail gate for release.

What is a requirements traceability matrix in QA?▼

A requirements traceability matrix (RTM) maps each atomic requirement to test scenarios across unit, API, UI, and end-to-end levels. It exposes coverage gaps, ambiguous requirements, and risk-based priorities so nothing ships untested.

When should I use UAT planning instead of automated e2e tests?▼

Use UAT planning when stakeholders need a human-executable sign-off plan or when behavior is hard to automate, such as multi-step wizards, PDF exports, or email delivery. Use automated e2e tools like Playwright for repeatable regression checks.

How do I design test data for edge cases?▼

Derive data from field constraints: boundary values, invalid formats, role and state combinations, and temporal edges like expirations. Package values by purpose with seeding and cleanup notes rather than improvising sample data.

What are the limitations of acceptance test planning skills?▼

This Skill produces human-executable plans only; it does not write or run automated tests, and it must not execute against production data. Features with no user-facing interface, like background jobs, are out of scope.