gsd-verify-work

Automate conversational UAT of built features with persistent state.

Updated Jan 28, 2025
One-click install
npx skills add https://github.com/aslaii/dotfiles --skill gsd-verify-work-aslaii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/aslaii/dotfiles/tree/main/claude/skills/gsd-verify-work
Command: npx skills add https://github.com/aslaii/dotfiles --skill gsd-verify-work-aslaii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating that Claude-built features work from the user perspective requires structured, repeatable testing with preserved context.

Core Features & Use Cases

  • Conversational UAT: Run end-to-end user acceptance tests via natural-language prompts, preserving session state across steps.
  • Automated diagnosis & planning: When a test fails, automatically diagnose gaps and propose fix plans for retry.
  • Phase-driven testing: Manage tests across multiple phases, producing Phase-UAT documentation for each iteration.

Quick Start

Describe the phase you want to test and let the verify-work workflow guide the conversational UAT session.

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 for features built by Claude?

Conversational UAT for built features is run by describing the phase you want to test, allowing the workflow to guide end-to-end user acceptance testing while preserving session state across steps.

What is phase-driven user acceptance testing and when do I need it?

Phase-driven user acceptance testing validates features across multiple development iterations, producing Phase-UAT documentation for each phase. It is needed when verifying built features requires structured, repeatable testing with preserved context.

Can I automatically diagnose issues and plan fixes when a user acceptance test fails?

Automated diagnosis and fix planning occurs when a conversational UAT test fails, automatically diagnosing gaps and proposing fix plans for retry without losing the persistent testing state.

Does feature verification require specific workflow templates to orchestrate tests?

Feature verification requires access to the verify-work workflow and UAT templates to orchestrate conversational tests end-to-end, ensuring structured testing and persistent state across validation phases.

What is the best way to validate features from the user perspective without losing context?

The best way to validate features from the user perspective is using conversational UAT, which automates end-to-end verification via natural-language prompts while preserving session state across steps for repeatable testing.