/gsd-verify-work

name: gsd-verify-work
description: "Validate built features through conversational UAT"
argument-hint: "[phase number, e.g., '4'] [--ws <name>]"
allowed-tools:
  - Read
  - Bash
  - Glob
  - Grep
  - Edit
  - Write
  - Agent

<arguments>$ARGUMENTS</arguments>

The text inside `<arguments>` is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed.

<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> @~/.claude/gsd-core/workflows/verify-work.md @~/.claude/gsd-core/templates/UAT.md </execution_context>

<context> Phase: the `<arguments>` block (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 `<required_reading>` blocks. </context>

<process> Execute end-to-end. Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing). </process>