uat-cyclelisted

______________________________________________________________________ ## 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` 1. Find the test case by ID 1. 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\] 1. 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` 1. Find the best matching test case(s) 1. If ambiguous, present options for the user to choose 1. Once selected, present as above ### If no argument was provided: 1. Read `docs/testing/UAT_COVERAGE.md` 1. Show the status summary table 1. List all test cases with status "Not Tested" (prioritized) or "Fail" (for retesting) 1. 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.,