gsd-verify-work

To run conversational UAT, invoke the testing workflow with an optional phase number to interactively validate features and capture results. It executes a single phase per test, preserving state to guide diagnosis and fix planning when issues are detected.

Phase-based feature validation is a testing approach that checks user-facing functionality within a single, isolated development phase. You need it to ensure specific built features match expectations before moving forward, preserving context for targeted diagnosis.

Persistent state maintains context across testing phases, enabling the system to track previous validations and diagnose issues accurately. When problems arise, it uses this preserved state to propose actionable fix plans for execution.

No, you cannot validate multiple phases at once because the workflow applies checks across a single phase per test. This single-phase constraint ensures accurate state preservation and precise diagnosis for the specific features being validated.

The UAT report uses a structured markdown format named {phase_num}-UAT.md. This output file documents clear gaps found during conversational testing and provides actionable fix plans for execution.