gsd-verify-work

Validate built features through conversational user acceptance testing and record results.

4|Updated Apr 11, 2026

Search Tags:#workflow #testing #verification #feature validation #uat #issue diagnosis

Ready to run

npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-verify-work-electroheadfx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-verify-work
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-verify-work-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps verify that built features actually work from a user's perspective, reducing the risk of shipping incomplete or broken behavior after implementation.

Core Features & Use Cases

Conversational UAT: Tests product behavior one scenario at a time through plain-text interaction rather than rigid scripted automation.
Persistent Test Tracking: Produces phase-based UAT documentation so results, gaps, and fixes can be reviewed and resumed later.
Issue Diagnosis and Fix Planning: When a problem is found, it records the defect, identifies likely gaps, and prepares the next execution step.
Use Case: A developer asks the Skill to validate a completed phase, observe the real user flow, and capture any failures before moving to implementation follow-up.

Quick Start

Use the gsd-verify-work skill to validate phase 4 and record the UAT results.

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 user acceptance testing for completed features?▼

Conversational UAT validates built features through plain-text interaction, testing product behavior one scenario at a time to confirm real user flows work before moving to implementation follow-up.

What is conversational UAT and how does it work for feature validation?▼

Feature validation through conversational UAT tests product behavior one scenario at a time via plain-text interaction rather than rigid scripted automation, observing real user flows to confirm completed phases.

Can I track UAT results and resume testing after finding an issue?▼

Persistent UAT tracking produces phase-based documentation so results, gaps, and fixes can be reviewed and resumed later, ensuring reliable handoff into execution after issue diagnosis.

How do I diagnose defects and plan fixes during post-build verification?▼

Issue diagnosis during post-build feature confirmation records the defect, identifies likely gaps, and prepares the next execution step for fix planning, ensuring reliable handoff into execution.

Does this verification workflow require any specific testing frameworks?▼

No, this verification workflow requires no external testing frameworks or dependencies, using conversational plain-text interaction to validate features and record phase-based results directly.

When should I use conversational UAT instead of rigid scripted automation?▼

Use conversational UAT for phase-based product verification when you need to observe real user flows flexibly, diagnose issues dynamically, and capture failures before moving to implementation follow-up.