/gsd-verify-work

name: gsd-verify-work
description: "Use after a phase executes, when the user wants to test the built features themselves. Runs one conversational UAT test at a time into {phase}-UAT.md and, when something fails, diagnoses it and queues fix plans for /gsd-execute-phase."
argument-hint: "[phase number, e.g., '4']"
allowed-tools:
  - Read
  - Bash
  - Glob
  - Grep
  - Edit
  - Write
  - Task

<objective> Validate built features through conversational testing with persistent state.

Purpose: Confirm what Claude built actually works from user's perspective. One test at a time, plain text responses, no interrogation. When issues are found, automatically diagnose, plan fixes, and prepare for execution.

Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed gaps, verified fix plans ready for /gsd-execute-phase </objective>

<execution_context> @$HOME/.claude/get-shit-done/workflows/verify-work.md @$HOME/.claude/get-shit-done/templates/UAT.md </execution_context>

<context> Phase: $ARGUMENTS (optional)

• If provided: Test specific phase (e.g., "4")
• If not provided: Check for active sessions or prompt for phase

Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks. </context>

<process> Execute the verify-work workflow from @$HOME/.claude/get-shit-done/workflows/verify-work.md end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process>