gsd-audit-uat

Scan planning phase markdown files for outstanding UAT and verification statuses.

Updated Aug 15, 2025
One-click install
npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-audit-uat-gesmith0606
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/gesmith0606/nfl_data_engineering/tree/main/.claude/skills/gsd-audit-uat
Command: npx skills add https://github.com/gesmith0606/nfl_data_engineering --skill gsd-audit-uat-gesmith0606

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds and consolidates outstanding user acceptance test (UAT) and verification items scattered across phase planning documents, surfaces blocked or stale tasks, and generates a prioritized human test plan so teams can resolve verification debt efficiently.

Core Features & Use Cases

  • Cross-phase scanning: Locate pending, skipped, blocked, and human_needed statuses across UAT and verification markdown files.
  • Staleness detection: Cross-reference findings against the codebase to flag documentation that no longer matches implementation.
  • Prioritized output: Produce a concise, prioritized human test plan for QA and product owners to action.
  • Use Case: Run a repository audit before a release to ensure all UAT blockers are identified, validated against current code, and assigned a remediation priority.

Quick Start

Run a scan of .planning/phases to list all *-UAT.md and *-VERIFICATION.md files, identify pending/skipped/blocked/human_needed items, cross-check related source files, and return a prioritized human 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 outstanding UAT items scattered across project phases?

You can consolidate outstanding UAT items by scanning planning phase markdown files matching *-UAT.md and *-VERIFICATION.md to aggregate pending, skipped, blocked, and human_needed statuses into a unified list.

What is a stale documentation detection audit for user acceptance testing?

Stale documentation detection cross-references outstanding UAT items against the repository source code to flag planning markdown files that no longer match the current implementation.

How do I generate a prioritized human test plan from verification markdown files?

Generate a prioritized human test plan by scanning verification markdown files for pending and blocked statuses, cross-checking related source files for staleness, and outputting a prioritized remediation list for QA.

Can I audit pending and blocked verification tasks without external dependencies?

Yes, you can audit pending and blocked verification tasks without external dependencies, as the scan requires only filesystem glob, read, grep, and optional bash access to parse phase markdown files.

When should I run a UAT repository audit before a release?

Run a UAT repository audit before a release to ensure all blocked or skipped verification items are identified, validated against current code for staleness, and assigned a remediation priority for QA.