gsd-verify-work

Validate built features through conversational user-acceptance testing with persistent state.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-verify-work-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-verify-work
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-verify-work-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate built features through conversational user-acceptance testing with persistent state.

Core Features & Use Cases

  • Conversational, phase-based verification of features with automatic diagnosis and remediation planning.
  • Manages session state across tests and routes results to remediation tasks.
  • Use case: QA teams validating Claude-built capabilities through end-to-end, phase-driven testing.

Quick Start

Run the verify-work workflow end-to-end to validate built features.

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 built features end-to-end?

Conversational UAT validates built features through phase-driven testing sessions with persistent state. You run the verify-work workflow end-to-end, executing tests across phases while the session state is managed automatically to track progress and route results.

What is conversational user acceptance testing with persistent state for feature verification?

Conversational UAT with persistent state is a phase-based testing approach that validates built features across multiple sessions. It manages test state continuously, diagnoses issues during execution, and generates actionable remediation plans for any failures encountered.

How do I diagnose and plan remediation for issues found during user acceptance testing?

Issue diagnosis during user acceptance testing is handled by routing test results to remediation tasks automatically. The workflow diagnoses failures across phased testing sessions and produces actionable remediation plans to resolve the detected problems.

Can I validate Claude-built capabilities across multiple testing sessions without losing state?

Yes, validating Claude-built capabilities across multiple testing sessions is supported through persistent state management. The workflow maintains session state continuously, ensuring end-to-end feature verification remains intact even when tests span across different phased execution periods.

What's the best way to manage test state for phase-driven integration testing workflows?

Managing test state for phase-driven integration testing is best handled through a conversational workflow with persistent state. This approach ensures session management tracks phased test execution continuously and automatically routes diagnostic results to actionable remediation tasks.

Why does my feature verification process lose context between testing phases?

Feature verification loses context between testing phases when persistent state management is absent. A conversational UAT workflow with persistent state resolves this by maintaining session data across phased testing executions and ensuring continuous diagnostic routing.