wa:validate-uat

To generate a UAT checklist from acceptance criteria, the workflow loads goals from TASKS.md or a feature description and builds a risk-prioritized checklist covering functional, edge case, and UX categories.

You cannot automate pass fail decisions during user acceptance testing here because the workflow enforces human confirmation gates, requiring explicit user-provided Pass, Fail, or Skip responses for every checklist item.

Human validation for UAT reporting works by gating each checklist item with explicit user confirmations, then using those Pass/Fail/Skip responses to produce a final PASS/FAIL verdict written to a UAT-REPORT.md file.

You do not strictly need a TASKS.md file to run a UAT validation workflow; you can provide a specific feature name or alternative goal source instead, though loading TASKS.md and DEV-NOTES.md provides optimal context.

You prioritize test cases for staging UAT planning by correlating acceptance criteria satisfaction signals from development notes, ordering checklist items by expected risk to focus on high-impact functional and edge case validations.