skills.rest
deerawan
deerawanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gsd-audit-uat

Cross-audit UAT and verification markdown files for pending, skipped, blocked, and human_needed items.

1|Updated Sep 6, 2015
Search Tags:#documentation#verification#audit#prioritization#test planning#uat#codebase sync
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-audit-uat-deerawan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-audit-uat
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-audit-uat-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find UAT items that are pending, skipped, blocked, or still marked for human action, and it catches mismatches where planning documentation has become stale versus the actual codebase.

Core Features & Use Cases

  • Cross-phase UAT scanning: Reviews multiple UAT-related phases (UAT and verification) to surface what still needs attention.
  • Prioritized human test planning: Turns findings into a ranked, actionable plan for human testing and follow-up.
  • Stale documentation detection: Cross-references planning artifacts against the codebase to identify outdated items.

Quick Start

Ask the AI to run the gsd-audit-uat workflow using the in-workflow planning files located under .planning/phases.

Frequently Asked Questions about gsd-audit-uat

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

FAQPage Schema
How do I find skipped or pending UAT items across multiple project phases?▼

A cross-phase UAT audit scans *-UAT.md and *-VERIFICATION.md files under .planning/phases to surface pending, skipped, blocked, and human_needed items. It cross-references these planning artifacts against the repository codebase to detect stale documentation and generate a prioritized human testing plan.

What is the best way to detect stale test planning documentation against a codebase?▼

Cross-referencing UAT and verification markdown files against the repository codebase detects stale test planning documentation. This approach identifies mismatches where planning artifacts have become outdated compared to the current code implementation, ensuring testing accuracy.

How do I prioritize human testing follow-up for blocked UAT items?▼

Running a cross-phase audit collects pending, skipped, blocked, and human_needed entries from verification markdown files to prioritize human testing follow-up. This generates a ranked, actionable plan for human testing and follow-up.

Does UAT verification require specific file formats or directory structures?▼

UAT verification requires glob-based scanning of *-UAT.md and *-VERIFICATION.md markdown files located within the .planning/phases directory. This specific structure allows the cross-audit to cross-reference results against the repository codebase effectively.

Why does my test planning documentation not match the current codebase implementation?▼

Test planning documentation becomes stale when code implementation changes without corresponding updates to UAT and verification markdown files. A cross-audit detects these mismatches by comparing planning artifacts against the actual repository codebase.

Related Skills

Explore More Product & Management Skills→
aslaiiaslaii

gsd-audit-uat

Audit UAT and verification items across planning phases to produce a prioritized human test plan.

Community
Intermediate
GenproMMGenproMM

gsd-audit-uat

Automate cross-phase UAT audits and generate prioritized human test plans.

Official
Intermediate
lgwanailgwanai
4

gsd-audit-uat

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

Community
Intermediate
D0NMEGAD0NMEGA
8

gsd-audit-uat

Audit UAT and verification items across project phases using path-globs.

Community
Advanced