gsd-verify-work

Automate user acceptance testing of Claude-built features with persistent state.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-verify-work-trucol270
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/TruCol270/salty-pickle/tree/main/.claude-skills/gsd-verify-work
Command: npx skills add https://github.com/TruCol270/salty-pickle --skill gsd-verify-work-trucol270

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate built features through conversational UAT with persistent state, ensuring issues are surfaced and actionable for the team.

Core Features & Use Cases

  • End-to-end conversational UAT with persistent state to verify Claude-built features from the user's perspective.
  • Automatic diagnosis, fix planning, and preparation for execution when issues are detected.
  • Generation of phase-specific documentation (e.g., 4-UAT.md) to track results and progress.

Quick Start

Run the verify-work workflow for phase 4 to validate the latest features and generate the 4-UAT.md document.

Frequently Asked Questions about gsd-verify-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run conversational UAT to validate features during development?

Conversational UAT validates features through interactive dialogue with persistent state, automatically diagnosing detected issues, planning fixes, and generating phase-specific UAT documentation to track verification results.

What is phase-based feature validation and when do I need it?

Phase-based feature validation verifies built features against user acceptance criteria at specific development milestones, ensuring issues are surfaced and actionable before progressing to the next phase.

How do I generate phase-specific UAT documentation for my project?

Generate phase-specific UAT documentation by running the verify-work workflow, which outputs phase artifacts like 4-UAT.md from a dedicated template to record validation results and diagnostic plans.

Can I automate user acceptance testing for Claude-built features?

Automate user acceptance testing for Claude-built features through conversational interaction with persistent state, which surfaces issues, enables diagnosis, and prepares actionable fix plans for the development team.

Does this UAT workflow support automatic diagnosis and fix planning?

Yes, the UAT workflow supports automatic diagnosis and fix planning by validating features conversationally, detecting issues during interaction, and preparing execution plans for the team.

What are the limitations of conversational testing for feature validation?

Conversational testing for feature validation requires the verify-work workflow environment and UAT templates to be properly configured, as it relies on persistent state and dialogue interaction to generate accurate phase-specific documentation.