gsd-audit-uat

Audits phase-level project docs and generates prioritized human test plans.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-audit-uat-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-audit-uat
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-audit-uat-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the difficulty of tracking fragmented UAT and verification items across multiple project phases, preventing stale documentation and ensuring all requirements are accounted for.

Core Features & Use Cases

  • Cross-Phase Auditing: Scans all UAT and verification markdown files to identify pending, blocked, or skipped items.
  • Codebase Synchronization: Cross-references audit findings against the actual codebase to detect discrepancies between documentation and implementation.
  • Prioritized Planning: Generates a clear, actionable test plan for human verification based on the audit results.

Quick Start

Invoke the audit process by typing $gsd-audit-uat to scan all project phases and generate a prioritized human 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 audit UAT and verification items across multiple project phases?

To audit UAT and verification items, use an automated cross-phase audit tool that scans phase-specific markdown files to identify pending or blocked tasks. This process cross-references documentation against the codebase to ensure requirements are fulfilled.

What is automated cross-phase UAT and how does it synchronize with the codebase?

Automated cross-phase UAT scans markdown documentation to find pending or skipped verification tasks. It synchronizes with the codebase by cross-referencing these documented items against the actual implementation state to detect discrepancies and prevent stale documentation.

How do I generate a prioritized human-readable test plan from markdown documentation?

You can generate a prioritized human-readable test plan by running an automated audit that analyzes pending, blocked, and human-needed tasks in markdown files. The audit cross-references the codebase to produce an actionable plan for human verification.

How do I track fragmented compliance and verification tasks without missing requirements?

Tracking fragmented compliance and verification tasks is handled by scanning all project phase markdown files to consolidate pending or blocked items. This comprehensive audit ensures all requirements are accounted for and prevents stale documentation across the project lifecycle.

Does this UAT audit approach work without external dependencies or components?

Yes, this UAT audit approach works without external dependencies or components. It operates independently to scan project phase markdown files, cross-reference the current codebase state, and produce a prioritized human-readable test plan.