gsd-audit-uat

Audit UAT and verification items across project phases to generate a prioritized test plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-phase audit of outstanding UAT and verification items to ensure nothing is missed and improve release confidence.

Core Features & Use Cases

  • Cross-phase UAT item discovery and prioritization
  • Verification item tracking aligned with codebase
  • Use Case: When a release has scattered UAT notes, generate a consolidated plan and assign testers.

Quick Start

Run the gsd-audit-uat workflow to scan all phases for pending UAT items and generate 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 consolidate scattered UAT notes into a prioritized test plan?

Cross-phase UAT audits identify and prioritize outstanding verification items across project planning files, surfacing stale or blocked tasks to drive a structured, prioritized human test plan.

What is a cross-phase UAT audit and how does it reduce release risk?

A cross-phase UAT audit reduces release risk by scanning project phase documents and codebase references to validate statuses, ensuring no pending verification items are missed before release.

How do I track stale or blocked verification items across project phases?

You can track stale or blocked verification items by applying an audit workflow across .planning/phases/*/*-UAT.md and *-VERIFICATION.md files to read core planning documents and validate item statuses.

Does this UAT audit tool require specific planning file formats to work?

Yes, the UAT audit requires specific planning file formats, specifically applying across .planning/phases/*/*-UAT.md and *-VERIFICATION.md files to read core planning documents and codebase references.

Can I generate a structured test plan for testers from existing planning documents?

Yes, you can generate a structured test plan for testers from existing planning documents by reading and validating statuses across phase files to produce a consolidated, prioritized human test plan.

When should I not use an automated UAT item discovery workflow?

You should not use an automated UAT item discovery workflow if your project lacks structured planning files like *-UAT.md or *-VERIFICATION.md, as the audit depends on reading these specific documents.