gsd-verify-work

Conversational user acceptance testing (UAT) validates software feature implementation through interactive prompts and plain-text feedback loops. This approach bridges the gap between code completion and production readiness by managing structured test sessions to ensure built features meet user requirements.

Automate validation workflows by invoking the verify work command followed by the specific phase number to test. The system operates within development environments to manage test sessions, automatically diagnose gaps when tests fail, and prepare fix plans for subsequent execution phases.

UAT progress tracking is managed via dedicated UAT markdown files that maintain state across complex development workflows. This session management approach ensures consistent validation across project phases by recording testing outcomes and contextual data within the development environment.

Yes, this validation approach requires integration with GSD workflow templates and context-aware agent spawning to ensure consistent validation across project phases. These dependencies are necessary to bridge the gap between code completion and feature verification.

The best way to prepare fix plans when UAT tests fail is through automated diagnosis, which identifies gaps during testing and automatically generates fix plans for subsequent execution phases. This ensures a structured transition from failure detection to resolution planning.

Automated conversational UAT should not be used when your development environment lacks GSD workflow templates or context-aware agent spawning capabilities. Without these integrations, the tool cannot maintain the required state tracking and consistent validation across project phases.