gsd-audit-uat

Cross-phase UAT audit identifies pending verification items across project phases, cross-references them with the codebase and documentation to detect stale or missing artifacts, and surfaces status and blockers to prevent delivery gaps.

Generating a prioritized human test plan requires running an audit workflow on the project repository to cross-reference pending UAT items with codebase artifacts, producing an actionable remediation and validation action list.

Detecting stale or missing documentation during UAT verification is possible by cross-referencing surfaced outstanding verification items against the current codebase and project documentation artifacts to pinpoint inconsistencies.

A cross-phase UAT audit requires a workflow anchor file named audit-uat.md along with core planning references to successfully process pending items and generate a prioritized test plan.

Cross-phase UAT verification prevents delivery gaps by identifying outstanding verification items across all project phases and explicitly surfacing their current status, blockers, and owners for remediation tracking.

Auditing UAT items without core planning references limits the ability to generate a prioritized test plan, as the workflow requires these references alongside the audit-uat.md anchor to produce actionable validation output.