gsd-audit-uat

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-phase UAT and verification processes often suffer from fragmentation across documentation, missing items, and inconsistent prioritization, leading to delays and unclear action items. This skill tightens the workflow by identifying pending, skipped, blocked, and human_needed items and surfacing a prioritized plan.

Core Features & Use Cases

  • Scan all phases for pending, skipped, blocked, and human_needed UAT items.
  • Cross-reference against the codebase to detect stale documentation.
  • Produce a prioritized human test plan.

Quick Start

Run the audit workflow to generate a prioritized UAT plan from the planning files.

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 pending and skipped UAT items across multiple planning phases?

You can audit pending and skipped UAT items by scanning planning files under .planning/phases/*/*-UAT.md and *-VERIFICATION.md to identify pending, skipped, blocked, and human_needed verification tasks across phases.

What is the best way to generate a prioritized human test plan from planning documentation?

The best way to generate a prioritized human test plan is cross-referencing outstanding UAT and verification items against the codebase to detect stale documentation and surface actionable testing workflows.

How do I identify blocked and human_needed verification tasks in my codebase planning files?

You can identify blocked and human_needed verification tasks by applying an audit workflow to .planning/phases/*/*-VERIFICATION.md files, which surfaces stale documentation and prioritizes remaining items for execution.

Can I detect stale UAT documentation by cross-referencing planning files with the codebase?

Yes, you detect stale UAT documentation by cross-referencing .planning/phases/*/*-UAT.md files against the current codebase to find inconsistencies and produce a prioritized human test plan.

Does cross-phase UAT audit work without external dependencies?

Yes, cross-phase UAT audit works without external dependencies, relying solely on internal .planning/phases/*/*-UAT.md and *-VERIFICATION.md files combined with codebase analysis to execute the audit-uat workflow.