uat

Generates UAT checklists from commits and planned crop and saves PASS/FAIL/CONDITIONAL PASS reports.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill uat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uat
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/5-Validate-UAT
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill uat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken releases by giving you a structured, human-observable user acceptance testing process that turns code changes into concrete pass/fail outcomes with an explicit ship/no-ship decision.

Core Features & Use Cases

  • Generates a UAT checklist from the codebase and recent changes: Converts commits and planned scope into happy paths, edge cases, and error flows organized by feature area.
  • Guides scenario-by-scenario testing with a real user: Walks through each scenario one at a time and captures results as Pass, Fail, or Blocked.
  • Produces a documented UAT report and rollout decision: Summarizes passed/failed/blocked scenarios and records a PASS / FAIL / CONDITIONAL PASS (with conditional requirements) outcome, then saves a report for auditability.

Quick Start

Use the skill by prompting the assistant with “/uat” (or “user acceptance test” / “UAT”) so it generates a full UAT plan, walks through every scenario with the user, and outputs a final ship/no-ship report.

Frequently Asked Questions about uat

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

FAQPage Schema
How do I generate a user acceptance testing checklist from recent code commits?

User acceptance testing checklists can be generated by converting recent commits and planned scope into happy paths, edge cases, and error flows organized by feature area. This provides structured scenario coverage before migrating users to a new version.

What is the best way to document a ship decision for a high-impact feature release?

To document a ship decision, run scenario-by-scenario testing with a real user to capture Pass, Fail, or Blocked results, then summarize outcomes into a saved UAT report containing a PASS, FAIL, or CONDITIONAL PASS verdict for auditability.

How do I walk through UAT scenarios one at a time with a real user?

You can walk through UAT scenarios one at a time by prompting the assistant to generate a full UAT plan, which guides you through each scenario sequentially and captures pass, fail, or blocked results during the human-in-the-loop testing process.

When do I need to run acceptance testing before a production change?

Acceptance testing is needed before migrating users to a new version and before launching high-impact or newly added features that may change existing behavior, ensuring release readiness through structured human-observable validation.

What happens if a scenario is blocked during user journey test planning?

If a scenario is blocked during user journey test planning, it is treated as a hard blocker requiring a fix and re-test, directly impacting the final UAT report and preventing a clean PASS outcome for the release.

Does user acceptance testing support conditional pass outcomes for release readiness?

User acceptance testing supports CONDITIONAL PASS outcomes, allowing you to record a ship decision with conditional requirements attached, provided no scenarios are currently blocked by hard blockers requiring a fix.