gsd-audit-uat

You can audit pending UAT and verification items by applying this Skill across planning phases to identify pending, skipped, blocked, and human_needed tasks. It cross-references the codebase to detect stale documentation and outputs a prioritized action plan.

To detect stale documentation, the Skill cross-references your codebase against phase planning files. It uses path-globs like .planning/phases/*/*-UAT.md and *-VERIFICATION.md to find mismatches between documented verification items and the actual codebase state.

The best way to generate a prioritized human test plan is to run a cross-phase UAT audit. The Skill reviews all planning phases, categorizes items by status such as blocked or human_needed, and outputs an executable plan for engineers and testers.

Yes, you can identify skipped or blocked verification tasks by applying this audit across all planning phases. It specifically surfaces pending, skipped, blocked, and human_needed items to give you a clear status overview of your project.

You need specific file path structures for the audit to work. The Skill leverages path-globs such as .planning/phases/*/*-UAT.md and *-VERIFICATION.md to locate and drive the cross-phase audit of your verification items.