verify-work

Automates end-to-end UAT workflows for validating new features with persistent session state.

Updated Nov 16, 2025

Search Tags:#automation #planning #testing #conversational #uat #feature-validation

Ready to run

npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill verify-work-rayofsteel-dhbw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-work
Source: https://github.com/RayOfSteel-DHBW/TeilAutoNeu/tree/main/.github/skills/verify-work
Command: npx skills add https://github.com/RayOfSteel-DHBW/TeilAutoNeu --skill verify-work-rayofsteel-dhbw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate built features through conversational testing with persistent state. Creates UAT.md that tracks test progress, survives /clear, and feeds gaps into plan-phase.md --gaps.

Core Features & Use Cases

Automates end-to-end UAT workflows for validating new features with persistent session state.
Builds and maintains UAT files from phase SUMMARY.md, presents tests one at a time, and logs outcomes for review.
Coordinates parallel diagnosis and planning workflows when issues are found, producing gap-ready plans and commit-ready results.

Quick Start

Create and run a UAT session from a SUMMARY.md by generating a phase-specific UAT, presenting tests one at a time, and updating results based on user feedback.

Frequently Asked Questions about verify-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate user acceptance testing for new features conversationally?▼

Automating user acceptance testing conversationally is achieved by generating a UAT.md file from a SUMMARY.md, presenting tests iteratively, and logging outcomes to track validation progress. This approach applies staged test execution and issue logging.

What is a conversational UAT workflow and how does it maintain state across sessions?▼

A conversational UAT workflow validates features through iterative test presentation and response processing. It maintains persistent state by generating a UAT.md file that tracks test progress and survives context clearing, ensuring validation continuity.

How do I log test gaps and feed them into planning fixes after feature validation?▼

To log test gaps and plan fixes, the UAT workflow processes test responses, diagnoses issues, and feeds identified gaps into plan-phase.md. This produces gap-ready plans and coordinates parallel diagnosis workflows for commit-ready results.

Can I use a SUMMARY.md to generate staged test executions for feature validation?▼

Yes, you can use a SUMMARY.md with testable deliverables to generate staged test executions. The workflow builds phase-specific UAT files from the SUMMARY.md, applies frontmatter-based metadata, and presents tests one at a time.

What is the best way to validate built features without losing test progress?▼

The best way to validate built features while retaining progress is to use a conversational testing approach that writes batched results to a persistent UAT.md file. This ensures test outcomes survive session resets and remain available for review.

Do I need a SUMMARY.md file to run end-to-end UAT workflows?▼

Yes, a SUMMARY.md containing testable deliverables is required to run end-to-end UAT workflows. The system reads this file to build the UAT file, generate frontmatter-based metadata, and initiate the iterative test presentation process.