gsd-audit-uat

To audit UAT items before release, recursively scan phase markdown planning files to identify pending, skipped, blocked, or human-needed verification tasks. This process consolidates open items so reviewers can focus on unresolved work.

Finding verification gaps requires cross-referencing planning notes against the codebase to surface outdated documentation. This staleness check identifies mismatched files and highlights items still requiring manual validation before milestone review.

Generating a prioritized human test plan involves scanning phase files for unresolved verification items and ordering them by risk, blockers, and status. The output directs manual testers toward the most critical pending tasks first.

Yes, you can check for stale documentation by cross-referencing planning markdown files against actual implementation evidence in the codebase. This surfaces outdated or mismatched notes so teams can update them before release.

Yes, UAT audit specifically targets skipped and blocked verification tasks alongside pending and human-needed items. It consolidates all these outstanding statuses across phases to ensure no unfinished work slips through release planning.