uat: should offer to fix failures after testing completes

[skytect]

Human Note	After rapid:uat finds issues, it should offer to fix them instead of just logging and moving on
Version	6.0.0
Skill	uat

Problem Statement

When UAT completes with failures, the skill logs the issues, writes artifacts, and exits with a "Next steps" banner pointing to bug-hunt or review summary. It never offers to fix the failures it just found.

This breaks the flow. The user has just identified concrete, well-scoped problems with clear acceptance criteria. The skill has all the context needed to attempt fixes (relevant files, expected behavior, actual behavior). Instead it forces the user to manually start a separate fix workflow.

Proposed Solution

After Step 8 (issue logging) and before Step 9 (completion banner), add a fix loop:

1. Present the list of failures with their severities
2. Prompt: "Fix these failures?" with options like "Fix all", "Fix critical only", "Skip"
3. For each failure to fix:
   • Read the relevant files
   • Propose a fix with a diff preview
   • Apply if approved, skip if rejected
4. Re-run the failed steps to verify the fix
5. Update REVIEW-UAT.md with the new results

This keeps the user in the UAT flow instead of forcing a context switch.

Current Workaround

User must manually fix failures after UAT exits, then re-run /rapid:uat to verify.

Related Issues

• uat: should investigate fix before asking severity #48 - uat: should investigate fix before asking severity (related UX gap in the same flow)

Co-Authored-By: Claude Opus 4.6 (1M context)