uat-cycle

name	UAT-cycle
version	2.4.0
description	Execute a UAT test case — select, test, process findings, fix or log, and close the cycle.
trigger	manual
depends-on	[]
references	[]
disable-model-invocation	true
user-invocable	true
allowed-tools	Read, Glob, Grep, Bash, Edit, Write
argument-hint	<test-case-id-or-description>

---

UAT-cycle

Executing UAT cycle: $ARGUMENTS

Phase 1: Select Test Case

If a test case ID was provided (e.g., UAT-001):

1. Read docs/testing/UAT_COVERAGE.md
2. Find the test case by ID
3. Present it to the user:
   • Test Case ID: UAT-###
   • Title: [title]
   • Covers: [backlog story IDs or feature area]
   • Prerequisites: [what's needed]
   • Steps: [numbered steps]
   • Acceptance Criteria: [checklist]
4. Ask: "Ready to start testing? Are all prerequisites met?"

If a description was provided instead of an ID:

1. Read docs/testing/UAT_COVERAGE.md
2. Find the best matching test case(s)
3. If ambiguous, present options for the user to choose
4. Once selected, present as above

If no argument was provided:

1. Read docs/testing/UAT_COVERAGE.md
2. Show the status summary table
3. List all test cases with status "Not Tested" (prioritized) or "Fail" (for retesting)
4. Ask the user to select which test case to execute

Phase 2: Execute Test

Persona Context Loading

If the test case's parent story has a Personas: field (not "internal"), load the referenced persona(s) from docs/context/personas.md. When persona context is available:

• Frame test guidance from the persona's perspective — use their context (device, proficiency, constraints) to inform how the test should be performed
• Present steps with persona awareness — e.g., "As [Name] ([Role]), try to [step]. Given their [constraint], watch for [specific friction point]."
• Evaluate results against the persona's EVALUATES BY questions in addition to the acceptance criteria
• Flag FAILURE LOOKS LIKE matches — if a test result resembles the persona's failure scenario, escalate severity

Skip when: No Personas: field on the story, personas.md doesn't exist, or the test case is purely technical (API contract, data migration, etc.).

Test Execution

The user performs the test steps manually (or with automation tooling). Claude assists by: