gsd-audit-uat

Audit outstanding UAT items across SDLC phases and generate prioritized human test plans.

Updated Apr 22, 2025

Search Tags:#audit #software testing #cross-referencing #uat #test plan generation

Ready to run

npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-audit-uat-mcampbellr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-audit-uat
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-audit-uat-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill simplifies the audit process of outstanding User Acceptance Testing (UAT) items by scanning and cross-referencing against the codebase, ultimately generating a prioritized human test plan.

Core Features & Use Cases

Comprehensive UAT Item Scanning: Checks all phases for pending, skipped, blocked, and human_needed items.
Documentation Validation: Cross-references UAT items against the codebase to identify stale documentation.
Prioritized Test Plan Generation: Produces a plan for human testing, based on item urgency and importance.
Use Case: A software team can use this Skill to ensure all UAT items are up-to-date before going live, improving product quality and reducing go-live risks.

Quick Start

Use the 'gsd-audit-uat' skill to audit UAT items in your project by executing the skill within your workflow.

Frequently Asked Questions about gsd-audit-uat

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

FAQPage Schema

How do I audit User Acceptance Testing items against my codebase?▼

Auditing User Acceptance Testing items involves scanning all software development lifecycle phases for pending, skipped, blocked, and human_needed items, then cross-referencing them against the codebase to detect stale documentation and generate a prioritized human test plan.

What is a cross-phase UAT audit and when do I need it?▼

A cross-phase UAT audit verifies the status of outstanding User Acceptance Testing items across the software development lifecycle to identify stale documentation. You need it before going live to improve product quality and reduce deployment risks.

How do I generate a prioritized human test plan from outstanding UAT items?▼

Generate a prioritized human test plan by scanning all project phases for pending, blocked, and human_needed UAT items, then evaluating their urgency and importance to produce a targeted testing schedule.

Do I need stow to execute the UAT audit workflow?▼

Yes, you need stow for environment management to execute the CLI-based workflow required for this UAT audit. It is necessary for managing the environment when cross-referencing items against the codebase.

How do I detect stale UAT documentation in my software project?▼

Detect stale UAT documentation by cross-referencing outstanding User Acceptance Testing items against the actual codebase to identify discrepancies where testing records no longer match the current code state.

What is the best way to track blocked and skipped UAT items across development phases?▼

The best way to track blocked and skipped UAT items is conducting a comprehensive cross-phase audit that scans all software development lifecycle stages. This approach ensures all pending items are verified and updated before release.