gsd-audit-uat

To automate the UAT audit process, use a skill that scans all project phases for pending, skipped, blocked, and human_needed verification items. It cross-references these items against your codebase to identify discrepancies and outdated documentation automatically.

A prioritized test plan is a generated schedule that ranks outstanding UAT verification items based on audit results and codebase cross-referencing. It guides human testers through critical pending or blocked items first, ensuring efficient quality compliance.

You can detect stale documentation by running an automated cross-phase audit that cross-references your outstanding UAT verification items against the actual codebase. This process highlights mismatches where project documentation no longer reflects the current code implementation.

Yes, you can scan all development phases for skipped or blocked UAT items. The cross-phase audit mechanism specifically targets these statuses alongside pending and human_needed items to ensure no outstanding verification tasks are missed.

The best way to generate a human test plan from outstanding verification items is to use an automated audit tool that cross-references UAT statuses with the codebase. This approach detects stale documentation and outputs a prioritized test plan for human verification.

No specific framework is required to cross-reference UAT items with a codebase. The audit process operates directly on your project environment and scripts to detect outdated documentation and produce a prioritized test plan without external dependencies.