gsd-verify-work

Run conversational user acceptance testing with persistent tracking state.

1|Updated May 24, 2026
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-verify-work-tinner-deinno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-verify-work
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-verify-work-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that newly built features actually work for real users by running one-by-one conversational UAT and tracking results with persistent state.

Core Features & Use Cases

  • Conversational UAT execution: Runs end-to-end tests as plain-text user-facing checks rather than interrogations, focusing on observable behavior.
  • Phase-scoped verification: Supports testing a specific phase number or determining which phase to run based on active sessions.
  • Issue diagnosis and fix planning: When problems are found, produces diagnosed gaps and verified fix plans ready for execution in the next routing step.

Quick Start

Ask an AI runtime to run gsd-verify-work and test phase 4 by saying: "Run /gsd-verify-work 4 and produce the {phase_num}-UAT.md tracking file with fix plans if issues are found."

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 to validate delivered software features?

Conversational UAT validates delivered software features through plain-text interactions that confirm observable behavior from the user perspective, tracking results with persistent state across testing sessions.

How does phase-based testing work for staged verification across build phases?

Phase-based testing targets a specific phase number or determines which phase to run based on active sessions, ensuring staged verification confirms outcomes for each build phase sequentially.

Can I generate fix plans automatically when bug diagnosis finds issues during user acceptance testing?

Yes, when bug diagnosis identifies problems during user acceptance testing, the workflow produces diagnosed gaps and verified fix plans ready for execution in the next routing step.

What's the best way to track UAT results with persistent state across multiple testing sessions?

Persistent state tracking maintains UAT results across sessions by generating phase-specific tracking files, ensuring verification outcomes remain accessible for workflow orchestration and routing readiness.

Does conversational testing work for validating features without requiring automated test scripts?

Yes, conversational testing runs end-to-end checks as plain-text user-facing interactions rather than script-based interrogations, focusing on observable behavior to validate features without automated test infrastructure.

When should I not use conversational UAT for software verification?

Conversational UAT may not suit scenarios requiring high-volume automated regression testing or performance load testing, as it focuses on plain-text interactive feature confirmation rather than scripted batch execution.