gsd-verify-work

Automate conversational user acceptance testing with persistent state and test tracking.

Updated May 28, 2026
One-click install
npx skills add https://github.com/SensLiao/Claude-code-setting --skill gsd-verify-work-sensliao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/SensLiao/Claude-code-setting/tree/main/skills/gsd-verify-work
Command: npx skills add https://github.com/SensLiao/Claude-code-setting --skill gsd-verify-work-sensliao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates conversational user acceptance testing, allowing you to validate built features efficiently and effectively through natural language conversations.

Core Features & Use Cases

  • Conversational UAT: Engage in dialogue-like conversations to verify functionality of built features.
  • Persistent State: Maintain state throughout the conversation to diagnose and plan fixes.
  • Test Tracking: Generate and track a document tracking all test results for a specified phase.

Quick Start

To start a test for phase 4, use the 'gsd-verify-work' skill with the argument '4'. Example: 'gsd-verify-work 4'.

Frequently Asked Questions about gsd-verify-work

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

FAQPage Schema
What is conversational user acceptance testing for feature validation?

Conversational user acceptance testing (UAT) validates built software features through natural language dialogue interactions. It simulates textual conversations to verify functionality while maintaining persistent state throughout the test to diagnose issues and track results.

How do I automate user acceptance testing for a specific development phase?

Automate UAT by invoking the testing skill with a phase number argument, such as '4'. This initiates the conversational feature validation for that phase, tracking all test results in a generated document for review.

Can I maintain test state across multiple conversational interactions during feature validation?

Yes, persistent state is maintained throughout the conversational UAT process. This allows the testing workflow to track context across interactions, helping diagnose failures and plan fixes without losing previous validation progress.

Does automated conversational testing require any external testing frameworks or dependencies?

No external testing frameworks or dependencies are required. The automated conversational UAT operates independently, using interaction simulation and state management to validate software features through textual conversation.

What's the best way to track test results across a conversational UAT workflow?

Use a test tracking document generated during the conversational UAT. This document tracks all test results for a specified phase, providing a persistent record of feature validation outcomes to review and diagnose failures.

When should I use conversational UAT instead of traditional automated testing scripts?

Use conversational UAT when validating built features requires natural language interaction simulation and persistent state management. It is suited for software validation workflows where textual dialogue better captures user acceptance criteria than rigid scripts.