uat-release

Coordinate user-acceptance testing and release decisions after integration tests pass.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill uat-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uat-release
Source: https://github.com/sohei56/maul-team/tree/main/skills/uat-release
Command: npx skills add https://github.com/sohei56/maul-team --skill uat-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents incomplete or unreliable releases by coordinating user-acceptance testing, defect tracking, and a controlled release decision after integration tests pass.

Core Features & Use Cases

  • Requirements-Based UAT: Exhaustively derive user stories from requirements, maintain FR-to-US traceability, and verify each story with a recorded verdict.
  • Evidence-Driven Defect Handling: Capture UAT transcripts, browser screenshots for UI checks, expected-versus-observed results, and route confirmed defects into refined backlog PBIs.
  • Release Governance: Enforce automated-test prerequisites, support agent or human product-owner workflows, apply integration-cycle limits, and regenerate project documentation before a successful release.
  • Use Case: After an integration sprint passes, use this Skill to walk the product owner through every release-relevant requirement, document failures, return defects to development when necessary, and complete the release only after the go/no-go gate is satisfied.

Quick Start

Use the uat-release skill after integration tests pass to conduct requirements-based UAT, record evidence and defects, and decide whether the release is ready.

Frequently Asked Questions about uat-release

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

FAQPage Schema
How do I conduct user acceptance testing after integration tests pass?

User acceptance testing after integration requires deriving user stories from requirements, verifying each story with recorded verdicts, capturing UI evidence like browser screenshots, and routing confirmed defects into backlog items before a go/no-go release decision.

What is requirements traceability in a Scrum release workflow?

Requirements traceability in a Scrum release workflow maps functional requirements to user stories and recorded UAT verdicts, ensuring every release-relevant requirement is verified before completing the release gate.

How do I track defects found during UAT and route them back to development?

Defect tracking during UAT involves capturing transcripts, browser screenshots, and expected-versus-observed results, then routing confirmed defects into refined product backlog items for development.

Can I automate the go/no-go release decision with product owner walkthroughs?

Yes, release governance supports both human and agent product-owner workflows to walk through requirements, document failures, and enforce automated test prerequisites before completing the release gate.

What prerequisites are required before starting UAT for a software release?

Starting UAT requires passing integration test results, complete UAT verdicts and transcripts, controlled state transitions, and release documentation regeneration to satisfy the release gate.

Why does my software release fail the go/no-go gate during UAT?

A release fails the go/no-go gate when UAT verdicts are incomplete, integration tests have not passed, confirmed defects remain un-routed to the backlog, or release documentation is not regenerated.