qsd-audit-uat

Audit UAT items across phases by status and flag stale documentation.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-audit-uat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-audit-uat
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-audit-uat
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-audit-uat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-phase audit of UAT items to surface pending, skipped, blocked, and human_needed tasks, while identifying stale or missing documentation by cross-referencing against the codebase, enabling a prioritized remediation plan.

Core Features & Use Cases

  • Cross-phase UAT health checks identify status flags across phases and surface gaps for action.
  • Documentation hygiene verifies UAT references against the codebase to surface stale or missing docs.
  • Prioritized remediation plan outputs concrete actions with suggested owners for QA, development, and product teams.

Quick Start

Run the audit workflow to enumerate and prioritize UAT items across all phases.

Frequently Asked Questions about qsd-audit-uat

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit UAT items and identify blocked or pending tasks across project phases?

Auditing UAT items involves identifying and classifying tasks across all project phases by status flags such as pending, skipped, blocked, and human_needed, which surfaces actionable gaps for project remediation.

What is the best way to detect stale documentation by cross-referencing UAT artifacts against the codebase?

Detecting stale documentation requires cross-checking phase artifacts matching UAT and verification patterns directly against the codebase to identify missing or outdated references and ensure documentation hygiene.

Can I generate a prioritized test plan with suggested owners for pending and skipped UAT verification tasks?

Yes, you can generate a prioritized, actionable test plan that outputs concrete remediation steps with suggested owners for QA, development, and product teams to integrate into the project workflow.

Does this UAT audit approach work without external dependencies for cross-phase verification?

Yes, the UAT audit approach works without external dependencies, analyzing phase artifacts and codebase references independently to classify task statuses and flag documentation gaps.

Why does my UAT documentation audit show stale docs when cross-checking verification patterns against the codebase?

Your UAT documentation audit shows stale docs because the cross-check detects phase artifacts matching verification patterns that no longer align with the current codebase references, indicating missing or outdated documentation.