gsd-verify-work

Automate end-to-end conversational UAT validation with persistent state and traceable test reports.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-verify-work-hadpadrahul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/hadpadrahul/school-erp/tree/main/.codex/skills/gsd-verify-work
Command: npx skills add https://github.com/hadpadrahul/school-erp --skill gsd-verify-work-hadpadrahul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that newly built features perform as intended through guided, conversational UAT, ensuring a reliable user experience before release.

Core Features & Use Cases

  • Maintains a persistent test state across multiple verification phases to reproduce and diagnose issues.
  • Automatically diagnoses gaps, plans fixes, and prepares execution steps for sign-off.
  • Generates phase-specific reports (e.g., 4-UAT.md) to document results and decisions.

Quick Start

Initiate a UAT session for a feature by invoking $gsd-verify-work and follow the prompts to capture test 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 perform conversational UAT to validate newly built features?

Conversational UAT validates built features by guiding test sessions with persistent state tracking. It captures results across multiple phases, diagnoses gaps, and prepares execution steps to ensure reliable user experience before release.

What is persistent state tracking in feature verification workflows?

Persistent state tracking in feature verification maintains test context across multiple phases. It enables accurate issue reproduction and diagnosis by preserving session data until fixes are planned and execution readiness is confirmed.

How do I generate structured test reports for UAT sign-off?

Structured test reports for UAT sign-off are generated as phase-specific plain-text files like 4-UAT.md. They document test outcomes, diagnosed gaps, and decisions to ensure reproducibility and traceability across verification phases.

Can I use non-interactive plain-text responses for automated feature validation?

Automated feature validation supports non-interactive plain-text responses to ensure reproducibility. This approach applies to conversational testing workflows where traceable test outcomes and phase tracking are required for sign-off.

What is the best way to diagnose gaps found during UAT phase tracking?

Diagnosing gaps during UAT phase tracking involves maintaining persistent test state to reproduce issues. The workflow automatically analyzes failures, plans fixes, and prepares execution steps for the next verification cycle.

Does UAT feature validation work across multiple test phases without losing state?

UAT feature validation works across multiple test phases by maintaining persistent state. It preserves session context and traceable outcomes throughout diagnosis, fix planning, and execution readiness checks for reliable sign-off.