gsd-audit-uat

Detect stale documentation during a UAT audit by applying cross-reference logic to compare planned tests against repository docs, which highlights mismatches and ensures your technical documentation aligns with actual test coverage.

Generate a prioritized human test plan for UAT remediation by aggregating skipped and human_needed verification statuses across multiple planning phases, then producing an actionable rollout schedule with owners and timelines.

Yes, you can audit multiple planning phases for blocked and skipped UAT items using cross-phase auditing, which aggregates verification statuses across your project phases to identify blockers and documentation gaps.

The best way to ensure documentation alignment before UAT rollout is to run documentation sanity checks that detect mismatches between planned tests and repository docs, ensuring technical alignment and UAT readiness.

Cross-phase UAT auditing works without specific external dependencies, relying entirely on scanning your planning directory and codebase to detect stale documentation and generate a prioritized test plan for remediation.