gsd-verify-work

Validate built features through conversational user acceptance testing.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-verify-work-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-verify-work
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-verify-work
Command: npx skills add https://github.com/coco-research/coco --skill gsd-verify-work-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates whether a built feature actually works from the user's perspective, reducing the risk of shipping incomplete or broken functionality.

Core Features & Use Cases

  • Conversational UAT: Test one scenario at a time in plain language instead of relying on rigid scripted checks.
  • Persistent Verification State: Track active sessions and phase context so testing can continue cleanly across interruptions.
  • Automatic Diagnosis and Fix Planning: When a test fails, identify the likely gap, outline the correction path, and prepare for execution.
  • Use Case: A developer finishes phase 4 of a feature and asks this Skill to verify the delivered behavior, capture issues, and produce a ready-to-execute follow-up plan.

Quick Start

Ask this skill to verify the current phase or a specific phase by running conversational user acceptance tests and reporting any issues with a ready fix plan.

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 a recently built feature?

Conversational user acceptance testing validates built features by testing one scenario at a time in plain language. It tracks active sessions and phase context to verify user-facing behavior cleanly across interruptions.

What is the best way to verify phased implementation behavior without rigid scripted checks?

Verifying phased implementation behavior through conversational user acceptance testing allows you to check user-facing functionality dynamically. It captures issues during the review and automatically diagnoses failures to ensure the delivered phase works correctly.

How do I automatically generate a fix plan when a user acceptance test fails?

When a user acceptance test fails, the verification process automatically diagnoses the likely gap and outlines a correction path. It prepares a ready-to-execute fix plan for downstream execution to resolve the identified behavioral issue.

Can I resume a feature validation session if my testing workflow is interrupted?

Yes, feature validation supports persistent state management to track active sessions and phase context. This allows testing to continue cleanly across interruptions, maintaining the exact session state needed for accurate behavioral verification.

Does session-based feature validation work for checking specific implementation phases?

Yes, session-based feature validation applies directly to phased implementation reviews. You can ask it to verify the current phase or a specific phase by running conversational user acceptance tests and reporting any issues with a ready fix plan.

Why use conversational UAT instead of standard automated testing for feature verification?

Conversational UAT validates whether a built feature actually works from the user's perspective, reducing the risk of shipping incomplete functionality. It tests scenarios in plain language and provides automatic failure diagnosis, unlike rigid scripted checks.