Files
msd-core/commands/gsd/verify-work.md
Lex Christopherson 9e0808b409 feat: redesign verify-work as conversational UAT with persistent state
- One test at a time instead of full checklist upfront
- Plain text responses instead of AskUserQuestion forms
- Severity inferred from description, never asked
- Persistent UAT.md survives /clear (like debug workflow)
- Single file per phase replaces per-plan ISSUES.md
- Updated plan-fix to read from UAT.md

Co-Authored-By: Claude <noreply@anthropic.com>
2026-01-14 09:56:17 -06:00

2.0 KiB

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

Output: {phase}-UAT.md tracking all test results, issues logged for /gsd:plan-fix

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

Phase: $ARGUMENTS (optional) - If provided: Test specific phase (e.g., "4") - If not provided: Check for active sessions or prompt for phase

@.planning/STATE.md @.planning/ROADMAP.md

1. Check for active UAT sessions (resume or start new) 2. Find SUMMARY.md files for the phase 3. Extract testable deliverables (user-observable outcomes) 4. Create {phase}-UAT.md with test list 5. Present tests one at a time: - Show expected behavior - Wait for plain text response - "yes/y/next" = pass, anything else = issue (severity inferred) 6. Update UAT.md after each response 7. On completion: commit, present summary, offer next steps

<anti_patterns>

  • Don't use AskUserQuestion for test responses — plain text conversation
  • Don't ask severity — infer from description
  • Don't present full checklist upfront — one test at a time
  • Don't run automated tests — this is manual user validation
  • Don't fix issues during testing — log for /gsd:plan-fix </anti_patterns>

<success_criteria>

  • UAT.md created with tests from SUMMARY.md
  • Tests presented one at a time with expected behavior
  • Plain text responses (no structured forms)
  • Severity inferred, never asked
  • File updated after each response (survives /clear)
  • Committed on completion
  • Clear next steps based on results </success_criteria>