gsd-audit-uat

Identify pending UAT and verification tasks and generate a prioritized human test plan.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-audit-uat-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-audit-uat
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-audit-uat-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams quickly find which UAT and verification items are still pending, skipped, blocked, or requiring human attention, and flags stale documentation by cross-checking against the codebase.

Core Features & Use Cases

  • Cross-phase UAT/verification inventory: Scans planning phases to surface outstanding items across multiple categories of work.
  • Staleness detection via codebase cross-reference: Compares planning artifacts against the current repository to detect outdated or no-longer-valid references.
  • Prioritized human test plan output: Produces an ordered list of what humans should verify first for maximum coverage and urgency.

Quick Start

Run the gsd-audit-uat skill to scan .planning/phases for all UAT and verification items, cross-reference them with the codebase, and generate a prioritized plan for human testing.

Frequently Asked Questions about gsd-audit-uat

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

FAQPage Schema
How do I identify pending and blocked UAT tasks across multiple release phases?

To identify pending UAT tasks, scan planning artifacts like .planning/phases/*/*-UAT.md and *-VERIFICATION.md. This process surfaces pending, skipped, blocked, and human_needed items across all phases to build a prioritized human test plan.

What is codebase cross-referencing for UAT verification?

Codebase cross-referencing for UAT verification is the process of comparing planning artifacts against the repository code to detect stale documentation and validate planning-to-code alignment for multi-phase release processes.

How do I generate a prioritized human test plan from planning documentation?

Generate a prioritized human test plan by scanning UAT and verification markdown files to discover outstanding status items, then ordering them by coverage urgency and rollout readiness for human testers.

Can I use filesystem globbing to detect stale UAT documentation in my repository?

Yes, you can use filesystem globbing on .planning/phases/*/*-UAT.md and *-VERIFICATION.md files to inventory status items and cross-reference them against the codebase to flag outdated or no-longer-valid references.