gsd-audit-uat

You can identify outstanding UAT and verification gaps by scanning planning markdown files to surface pending, skipped, blocked, or human-needed items, then cross-referencing them against the current codebase to ensure documentation consistency.

Detect documentation staleness by cross-referencing your UAT and verification planning artifacts against the actual repository content, which flags mismatches to prevent tests and docs from drifting.

Generate a prioritized human test plan by applying glob patterns to read planning markdown files, validating the items against the codebase, and producing an ordered set of actions that focus on the highest-impact gaps first.

Yes, you can automate test planning reconciliation by scanning your repository to correlate pending, skipped, or blocked verification items across planning phases and outputting a prioritized list of required human actions.

Yes, the UAT audit workflow cross-reference works by reading standard planning markdown files via glob patterns, specifically targeting files like UAT and verification documents to validate them against repository content.

You should not use automated UAT gap analysis if your engineering workflow lacks markdown planning files to scan, as the process requires reading these artifacts to cross-reference against the codebase and produce a human test plan.