gsd-verify-work

Run conversational end-to-end UAT and write phase-specific tracking reports.

Updated May 21, 2026
One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-verify-work-jedmamosto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-verify-work
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-verify-work-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It confirms that newly built features actually work from a user’s point of view by running conversational, end-to-end UAT with persistent tracking.

Core Features & Use Cases

  • Conversational UAT with gates: Executes phase-aware testing while preserving workflow gates for session management, test presentation, diagnosis, fix planning, and routing.
  • Phase-focused validation: Lets you test a specific phase number (or continue with active sessions) to verify incremental progress without redoing everything.
  • Issue diagnosis and fix planning: When a failure or gap is detected, it diagnoses the underlying issue and prepares verified fix plans for execution.
  • Persistent results tracking: Writes output to a phase-specific report file named {phase_num}-UAT.md to keep a clear history of what was tested and what changed.

Quick Start

Run gsd-verify-work for phase 4 and review the generated {phase_num}-UAT.md results to confirm behavior end-to-end.

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 specific build phases?▼

Run conversational UAT by providing a specific phase number or using active session detection to execute end-to-end conversational checks for incremental progress validation.

What is the best way to validate delivered features from a user perspective?▼

Feature validation from a user perspective is done through conversational UAT that surfaces real failures by applying end-to-end checks while preserving workflow gates for session management.

How do I diagnose issues and plan fixes during user acceptance testing?▼

Issue diagnosis and fix planning during UAT automatically triggers when a failure or gap is detected, diagnosing the underlying issue and preparing verified fix plans for execution.

Can I track feature validation results persistently across testing sessions?▼

You can track feature validation results persistently because the system writes output to a phase-specific report file named {phase_num}-UAT.md to maintain a clear testing history.

Does phase-based testing require redoing previous validation steps?▼

Phase-based testing does not require redoing previous validation steps, as it lets you verify incremental progress by focusing testing on a specific phase number or active sessions.