gsd-verify-work

Conversational user acceptance testing validates built features by presenting one test at a time in plain text and recording outcomes. It confirms delivered functionality matches user expectations and maintains a clear audit trail.

Documenting UAT outcomes is handled by outputting a persistent {phase_num}-UAT.md tracking file. This file captures test results, diagnoses gaps, and generates verified fix plans ready for execution by the engineering team.

Conversational testing diagnoses failures by identifying gaps when a test fails, creating verified fix plans, and preparing work for execution. It resolves workflow templates to route results into execution phases.

You can run phase-specific verification sessions by applying the skill to individual project phases. It runs one test at a time, captures outcomes, and iterates on fixes to confirm a completed feature meets acceptance criteria.

Workflow templates and context files are read by the skill to produce the persistent UAT tracking file. It uses Read, Bash, Glob, Grep, Edit, Write, and Task tool calls as allowed to resolve these files and output diagnoses.

Conversational testing presents one test at a time in plain text to validate features from an end-user perspective. Unlike automated validation, it captures outcomes with persistent state and iterates on fixes interactively.