What problem does it solve? Teams approaching go-live often lack a structured, signable record that business stakeholders actually validated the system against real workflows. This Skill produces a complete UAT document — scenarios, entry/exit criteria, defect log, and a formal sign-off form — so acceptance is documented and traceable rather than verbal. ## Core Features & Use Cases - UAT Plan Generation: Creates a full UAT plan with schedule, team roles, RACI matrix, entry/exit criteria, and prioritized business scenarios written to documentation/09-quality/uat.md. - Sign-off Form: Produces a formal acceptance declaration with defect summary, known-issues register, and sponsor signature block. - Governed Workflow: Enforces prerequisite signatures (test-plan, functional-spec), validation rules, and a sources file before the QA Lead can sign. - Use Case: Before deploying a customer portal, run this Skill to generate UAT scenarios for registration and order placement, have business testers execute them, and capture the sponsor's formal acceptance. ## Quick Start Ask the agent to create the UAT documentation for your project once the test plan and functional specification are signed.
