gsd-audit-uat

Identify pending, skipped, blocked, and human_needed UAT items across project phases.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-audit-uat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/onelee85/my-skills/tree/main/gsd-audit-uat
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-audit-uat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-phase audit of all outstanding UAT and verification items. This Skill identifies pending, skipped, blocked, and human_needed UAT items and cross-references the codebase to detect stale documentation, enabling a prioritized remediation plan.

Core Features & Use Cases

  • Cross-phase item discovery: identifies pending, skipped, blocked, and human_needed UAT items across phases.
  • Codebase verification: cross-references findings against the repository to detect stale or missing documentation.
  • Prioritized test plan: generates an actionable, prioritized plan with owners and timelines for remediation.

Quick Start

Run a cross-phase audit to identify all pending UAT items, verify against the codebase, and output a prioritized test plan.

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 items across all project phases?

To identify pending and blocked UAT items across project phases, you can run a cross-phase audit that scans for skipped and human_needed verification tasks, and then cross-references the codebase to detect stale documentation.

How do I detect stale documentation in my codebase during a UAT audit?

Detecting stale documentation during a UAT audit involves cross-referencing identified pending and blocked verification items against the actual codebase to find gaps, missing details, or outdated references that require remediation.

What is the best way to generate a prioritized human test plan for UAT remediation?

The best way to generate a prioritized human test plan for UAT remediation is to audit all outstanding verification items, verify them against the codebase, and output an actionable plan with specific tasks, owners, and timelines.

Can I use a cross-phase audit to find skipped or human_needed UAT tasks?

Yes, a cross-phase audit can find skipped or human_needed UAT tasks by scanning all project phases to identify outstanding verification items and cross-referencing the findings against the codebase to ensure documentation accuracy.

Does a UAT audit provide actionable owners and timelines for outstanding verification items?

A UAT audit provides actionable owners and timelines by taking the identified pending, blocked, and skipped verification items and producing a prioritized human test plan with specific tasks and schedules for remediation.

What are the limitations of auditing UAT items without cross-referencing the codebase?

Auditing UAT items without cross-referencing the codebase limits the detection of stale documentation and gaps, meaning the resulting prioritized test plan may include outdated references or miss necessary remediation actions.