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.