msd-core/commands/gsd/verify-work.md at 341bf3e4eea42f8014e2e70b6bae744dddaef0fd

Files

Lex Christopherson e5624d3b77 refactor(09-01): simplify verify-work command to delegate to workflow

- References verify-work.md workflow and uat-issues.md template
- Inline step details moved to workflow
- Process section reduced to delegation pattern
- Matches GSD command conventions (discuss-phase.md style)

2026-01-08 08:57:49 -06:00

2.3 KiB

Raw Blame History

name, description, argument-hint, allowed-tools

name

description

argument-hint

allowed-tools

gsd:verify-work

Guide manual user acceptance testing of recently built features

[optional: phase or plan number, e.g., '4' or '04-02']

Read

Bash

Glob

Grep

Edit

Write

AskUserQuestion

Guide the user through manual acceptance testing of recently built features.

Purpose: Validate that what Claude thinks was built actually works from the user's perspective. The USER performs all testing — Claude generates the test checklist, guides the process, and captures issues.

Output: Validation of features, any issues logged to phase-scoped ISSUES.md

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

Scope: $ARGUMENTS (optional) - If provided: Test specific phase or plan (e.g., "4" or "04-02") - If not provided: Test most recently completed plan

Load project state: @.planning/STATE.md

Load roadmap: @.planning/ROADMAP.md

1. Validate arguments (if provided, parse as phase or plan number) 2. Find relevant SUMMARY.md (specified or most recent) 3. Follow verify-work.md workflow: - Extract testable deliverables - Generate test checklist - Guide through each test via AskUserQuestion - Collect and categorize issues - Log issues to `.planning/phases/XX-name/{phase}-{plan}-ISSUES.md` - Present summary with verdict 4. Offer next steps based on results: - If all passed: Continue to next phase - If issues found: `/gsd:plan-fix {phase} {plan}` to create fix plan

<anti_patterns>

Don't run automated tests (that's for CI/test suites)
Don't make assumptions about test results — USER reports outcomes
Don't skip the guidance — walk through each test
Don't dismiss minor issues — log everything user reports
Don't fix issues during testing — capture for later </anti_patterns>

<success_criteria>

Test scope identified from SUMMARY.md
Checklist generated based on deliverables
User guided through each test
All test results captured (pass/fail/partial/skip)
Any issues logged to phase-scoped ISSUES.md (not global)
Summary presented with verdict
User knows next steps based on results </success_criteria>

2.3 KiB Raw Blame History

2.3 KiB

Raw Blame History