gsd-audit-uat

Audit outstanding UAT and verification items across repository release readiness workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly release delays by identifying pending, skipped, blocked, or human-dependent UAT items and finding where verification and documentation lag behind the codebase.

Core Features & Use Cases

  • Cross-phase UAT & verification scan: Reviews outstanding UAT and verification work across multiple planning phases to surface what is still unresolved.
  • Codebase cross-referencing for stale artifacts: Detects UAT and verification items that no longer match the current implementation, including outdated or missing references.
  • Prioritized human test plan output: Produces a ranked set of what to test next, explicitly calling out items requiring human attention.

Quick Start

Run the gsd-audit-uat skill to scan all UAT and verification planning files, cross-check them against the repository, and generate a prioritized human test plan for what remains pending.

Frequently Asked Questions about gsd-audit-uat

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

FAQPage Schema
How do I audit outstanding UAT items for release readiness?▼

UAT audits surface pending, skipped, blocked, or human-dependent items by scanning verification markdown files across planning phases and cross-referencing the repository to generate a prioritized human test plan.

How do I detect documentation drift in my codebase before release?▼

Documentation drift is detected by cross-referencing UAT and verification items against the repository, flagging outdated or missing references where verification and documentation lag behind the codebase.

What is a prioritized human test plan and how is it generated?▼

A prioritized human test plan is a ranked set of what to test next, generated by scanning outstanding UAT and verification work and explicitly calling out items requiring human attention.

Can I use UAT markdown files to find skipped or blocked verification work?▼

Yes, UAT markdown files are globbed and scanned to find what is still unresolved, effectively surfacing skipped, blocked, or pending verification work across multiple planning phases.

Does regression preparation require cross-referencing the repository for stale artifacts?▼

Yes, cross-referencing the repository detects UAT and verification items that no longer match the current implementation, which is essential for regression preparation and finding stale artifacts.