verify-work

Automating user acceptance testing conversationally is achieved by generating a UAT.md file from a SUMMARY.md, presenting tests iteratively, and logging outcomes to track validation progress. This approach applies staged test execution and issue logging.

A conversational UAT workflow validates features through iterative test presentation and response processing. It maintains persistent state by generating a UAT.md file that tracks test progress and survives context clearing, ensuring validation continuity.

To log test gaps and plan fixes, the UAT workflow processes test responses, diagnoses issues, and feeds identified gaps into plan-phase.md. This produces gap-ready plans and coordinates parallel diagnosis workflows for commit-ready results.

Yes, you can use a SUMMARY.md with testable deliverables to generate staged test executions. The workflow builds phase-specific UAT files from the SUMMARY.md, applies frontmatter-based metadata, and presents tests one at a time.

The best way to validate built features while retaining progress is to use a conversational testing approach that writes batched results to a persistent UAT.md file. This ensures test outcomes survive session resets and remain available for review.

Yes, a SUMMARY.md containing testable deliverables is required to run end-to-end UAT workflows. The system reads this file to build the UAT file, generate frontmatter-based metadata, and initiate the iterative test presentation process.