shine-verify-work

Conversational UAT for feature validation runs by initiating a verify-work workflow for the active phase. It preserves session context across prompts to test one feature at a time and outputs a phase-specific UAT document.

Stateful user-acceptance testing preserves context across multiple prompts during a single verification session. You need it to diagnose issues and plan fixes across conversational interactions without losing previous test state.

Yes, diagnosing issues and planning fixes is built into the UAT session. After identifying problems during feature validation, it automatically routes issues for execution within an end-to-end workflow.

You generate a phase-specific UAT document by initiating the verify-work workflow for your active phase. The resulting file, such as 4-UAT.md, records the validation results for that specific development phase.

Yes, conversational UAT applies specifically to one-test-at-a-time verification sessions. It maintains persistent session context across prompts to ensure seamless stateful testing for each individual feature.

Stateful UAT is limited to one-test-at-a-time verification sessions within a phase-specific workflow. It does not handle parallel testing and focuses on diagnosing issues and routing fixes sequentially within its end-to-end workflow.