gsd-audit-uat

Audit UAT items across phases and generate prioritized test plans.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-audit-uat-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-audit-uat
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-audit-uat-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits across UAT and verification phases to surface outstanding items, misclassifications, and documentation gaps, enabling proactive remediation.

Core Features & Use Cases

  • Cross-phase item discovery and status triage (pending, skipped, blocked, human_needed)
  • Codebase cross-reference to detect stale or missing documentation
  • Prioritized, human-readable test plans with owners and remediation steps

Quick Start

Run the audit to enumerate all outstanding UAT items across phases and generate a prioritized test plan.

Frequently Asked Questions about gsd-audit-uat

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

FAQPage Schema
How do I identify and triage outstanding UAT items across different testing phases?

To identify outstanding UAT items, run an audit that enumerates tasks across all verification phases and triages them as pending, skipped, blocked, or human_needed. This classification surfaces misclassifications and enables proactive remediation before generating a test plan.

What is the best way to generate a prioritized UAT test plan within sprint boundaries?

Generate a prioritized UAT test plan by cross-referencing outstanding items against the codebase and living documentation. This produces a deterministic plan containing scope, owners, dependencies, and concrete resolution steps within current sprint boundaries.

How do I detect stale or missing documentation gaps in my codebase before UAT?

Detect stale or missing documentation gaps by cross-referencing your UAT items against the codebase and living documentation. This audit surfaces gaps and flags outdated records, ensuring your verification phases proceed with accurate technical context.

Can I audit my verification phases to find blocked or skipped test items?

Yes, you can audit verification phases to discover and triage all UAT items, specifically flagging those marked as blocked or skipped. The audit cross-references these items against the codebase to provide actionable remediation steps and owners.

What do I need to produce an actionable test plan with owners and dependencies?

Producing an actionable test plan requires auditing outstanding UAT items and cross-referencing them against the codebase and living documentation. This yields a deterministic plan with scope, owners, dependencies, and concrete steps to resolve each item.