gsd-audit-uat

To identify pending or skipped UAT items across release phases, scan .planning/phases/*/*-UAT.md and *-VERIFICATION.md files to locate blocked and human_needed verification tasks, cross-referencing them against the codebase to flag stale documentation.

The best way to triage a verification backlog for release readiness is to audit planning markdown files for human_needed and blocked items, then generate a prioritized human test plan focused on remaining risk and validation needs.

Cross-referencing UAT documentation against a codebase detects stale verification items by scanning planning phase markdown files and matching their tracked tasks with current codebase states, flagging outdated or no-longer-relevant entries for removal.

Yes, you can use glob-based collection to scan .planning/phases/*/*-UAT.md and *-VERIFICATION.md files, extracting blocked, pending, skipped, and human_needed QA items to evaluate overall release readiness across multiple phases.

A prioritized human test plan for UAT is a ranked list of validation tasks derived from scanning verification markdown files, needed when cross-phase work gets stuck with blocked or pending items to ensure focused release readiness.

Cross-phase UAT work gets stuck with stale verification items because pending, skipped, or human-blocked tasks in planning markdown files are rarely re-checked against the codebase, leading to outdated documentation and delayed releases.