verify-work

Name: verify-work
Availability: InStock
Author: VirtEngine

Conduct conversational UAT with persistent state and generate UAT.md.

17|4|Updated Oct 8, 2021

Search Tags:#planning #testing #stateful #gap-analysis #uat #conversational-testing

Ready to run

npx skills add https://github.com/virtengine/virtengine --skill verify-work-virtengine

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates built features through conversational testing by maintaining persistent state across sessions, enabling continuous verification and gap-fed planning.

Core Features & Use Cases

Conversational UAT: Engage in dialogue-driven testing that tracks outcomes and captures gaps for future work.
Persistent State: Survives /clear and carries context to successive tests, enabling end-to-end validation and traceability.
Plan-Phase Integration: Automatically feeds identified gaps into the plan-phase workflow for remediation.

Quick Start

Start a UAT session for a feature, run tests conversationally, and generate a UAT.md that tracks progress and feeds gaps into plan-phase.

Frequently Asked Questions about verify-work

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

FAQPage Schema

How do I conduct conversational UAT to validate features and track unresolved gaps?▼

Conversational UAT validates features through dialogue-driven testing, tracking outcomes and capturing gaps for future work. It generates a UAT.md file to record progress and feeds unresolved issues into the plan-phase for remediation.

Can I maintain persistent testing state across multiple sessions for end-to-end validation?▼

Persistent state maintains testing context across sessions, surviving context clears to carry validation data forward. This enables continuous end-to-end verification and ensures full traceability across successive conversational UAT cycles.

What is the best way to automatically feed gap analysis results into a planning workflow?▼

Gap analysis results are automatically fed into the plan-phase workflow for remediation and traceability. This integration ensures identified feature gaps during conversational testing are directly resolved in subsequent planning cycles.

How do I generate a UAT.md file to record build verification progress and outcomes?▼

Generate a UAT.md file by starting a conversational UAT session to validate built features. This file records testing progress, identified gaps, and final outcomes, serving as a persistent state reference for future sessions.

Does this feature validation approach require any specific testing dependencies or frameworks?▼

No specific testing dependencies or frameworks are required. Feature validation relies entirely on conversational testing mechanics and persistent state management to coordinate multi-step sessions and generate outcome records.

When should I use conversational testing instead of traditional automated testing scripts?▼

Use conversational testing when validating features requires multi-step dialogue, persistent state tracking across context clears, and direct integration with plan-phase workflows for gap remediation and traceability.