uat-generate

Generate complete UAT packages with traceability matrices and acceptance sections.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delivers structured, auditable UAT packages that enable customers and Product Owners to formally validate a delivery against requirements and acceptance criteria without manual, unpredictable processes.

Core Features & Use Cases

  • Generates a complete UAT package containing a header, delivery summary, requirements traceability matrix, UAT test cases, and a findings register.
  • Produces a reusable template format for acceptance decisions, including sign-off sections and coverage metrics.
  • Applicable after QA validation and before delivery acceptance, suitable for customer demos, audits, and formal reviews.

Quick Start

Provide the delivery ID, approved requirements, acceptance criteria, and delivery metadata to generate a ready-to-submit UAT package.

Frequently Asked Questions about uat-generate

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

FAQPage Schema
How do I generate a UAT package for formal software acceptance?

A UAT package formalizes customer validation of software deliveries by providing a structured set of documents. It includes a delivery summary, requirements traceability matrix, UAT test cases, findings register, and acceptance decision section to ensure auditable validation.

When do I need to create UAT test cases for delivery acceptance?

To create UAT test cases, input the delivery ID, approved requirements, and acceptance criteria. The generation process outputs test cases mapped within a requirements traceability matrix, alongside a findings register and coverage metrics for complete validation.

Does generating a requirements traceability matrix require approved acceptance criteria?

Generating a UAT package requires approved requirements, acceptance criteria, and delivery metadata as inputs. This suits product owners needing to validate scope and delivery readiness after QA validation but before formal acceptance.

What is the best way to formalize customer validation for a software delivery?

Unlike manual or unpredictable validation processes, a structured UAT package provides an auditable, reusable template format. It standardizes acceptance decisions by embedding coverage metrics and sign-off sections directly into the delivery review.

Can I use a UAT package template for both customer demos and formal audits?

A UAT package should not be used before QA validation is complete. It is specifically designed for the phase after QA validation and before delivery acceptance, ensuring the product owner validates already-tested delivery readiness.