gsd-verify-work

Run conversational user acceptance testing and generate phase-specific UAT results.

4|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-verify-work-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-verify-work
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-verify-work-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the risk of shipping “built” work that does not actually work for the user by running conversational, phase-based UAT and producing evidence-backed results.

Core Features & Use Cases

  • Conversational UAT validation: Confirms user-perceived behavior through plain-text, one-test-at-a-time interactions with persistent session state.
  • Phase-scoped testing: Optionally targets a specific phase number to verify incremental work without repeating completed checks.
  • Diagnose and plan fixes: When issues appear, it diagnoses gaps, verifies fix plans, and prepares them for the corresponding execution flow.

Use case: After a system or feature is implemented across multiple phases, use this Skill to validate what the end user experiences, capture results into a phase tracking file, and ensure any required changes are ready to execute.

Quick Start

Run gsd-verify-work to execute conversational UAT for the current or specified phase and generate a {phase_num}-UAT.md results tracker.

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 user acceptance testing for iterative feature delivery?

Conversational user acceptance testing validates built features through plain-text, one-test-at-a-time interactions with persistent session state to confirm user-perceived behavior across delivery phases.

How does phase-scoped UAT testing handle incremental work without repeating completed checks?

Phase-scoped UAT testing targets a specific phase number to verify incremental work, ensuring persistent session state prevents repeating completed checks during iterative feature validation.

What is the best way to diagnose gaps and plan fixes after a UAT session?

Diagnosing gaps after a UAT session involves automatic diagnosis of user-perceived issues and verifying fix plans to prepare them for subsequent execution flow.

How do I track user acceptance testing results for a specific delivery phase?

Tracking user acceptance testing results requires generating a phase-scoped markdown file named {phase_num}-UAT.md, which captures evidence-backed validation results for the current delivery phase.

Can I validate user-perceived behavior without automated test scripts?

Yes, you can validate user-perceived behavior through conversational testing, which confirms features using plain-text interactions instead of relying on automated test scripts.

Why does conversational testing require persistent session state?

Conversational testing requires persistent session state to maintain context across one-test-at-a-time interactions, ensuring accurate phase-scoped execution and structured results tracking.