uat-review

Validate UAT packages for requirements coverage, traceability, and readiness.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill uat-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uat-review
Source: https://github.com/mahg-es/araya/tree/main/skills/uat-review
Command: npx skills add https://github.com/mahg-es/araya --skill uat-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UAT packages generated automatically may have gaps in coverage or incomplete traceability. This skill validates the artifact before customer review, ensuring readiness.

Core Features & Use Cases

  • Requirements coverage checks: verifies every requirement has at least one acceptance criterion.
  • Traceability validation: ensures all links and mappings between requirements, ACs, and tests are present and valid.
  • Release readiness reporting: generates a concise findings report with clear acceptance decisions and actionable gaps.
  • Use Case: before customer submission, run this skill to confirm UAT readiness and surface any gaps needing attention.

Quick Start

Submit the UAT ID and the full UAT package to validate readiness.

Frequently Asked Questions about uat-review

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

FAQPage Schema
How do I validate requirements coverage and traceability in a UAT package?

To validate requirements coverage and traceability in a UAT package, apply checks verifying every requirement has an acceptance criterion and every criterion has a test case. This surfaces structural gaps before customer review.

What is UAT release readiness validation and when do I need it?

UAT release readiness validation is the process of checking a UAT package for missing acceptance criteria or broken traceability links. You need it before customer submission to ensure the artifact is complete.

Can I automatically generate a findings report for UAT acceptance testing gaps?

Yes, you can generate a structured findings report for UAT acceptance testing that outputs a prioritized gaps list and a decision of READY, NEEDS FIXES, or REJECTED based on test artifact validation.

What is the best way to check if every acceptance criterion has a UAT test case?

The best way to check if every acceptance criterion has a UAT test case is to run traceability validation across the UAT artifact that verifies all mappings are present, producing a prioritized list of missing links.

Does UAT validation work for automatically generated testing packages with missing links?

Yes, UAT validation works for automatically generated testing packages by identifying coverage gaps and incomplete traceability, specifically surfacing missing links between requirements, acceptance criteria, and test cases.

Why does my UAT package get rejected during customer review for traceability gaps?

A UAT package gets rejected during customer review for traceability gaps when requirements lack acceptance criteria or test cases lack valid links. Running pre-submission validation produces a prioritized gaps list to fix these issues.