skills.rest
rkz91
rkz91COMMUNITY
Explore all skills by this author →
GitHub

gsd-audit-uat

Scan UAT and verification files to generate a prioritized audit plan.

264|11|Updated Apr 25, 2026
Search Tags:#planning#testing#codebase#verification#audit#workflows#uat
One-click install
npx skills add https://github.com/rkz91/coco --skill gsd-audit-uat-rkz91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-audit-uat
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-audit-uat
Command: npx skills add https://github.com/rkz91/coco --skill gsd-audit-uat-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill scans and consolidates outstanding UAT items across multiple phases, surfacing blockers and generating a prioritized human-test plan to keep product development moving.

Core Features & Use Cases

  • Cross-phase UAT item discovery: identifies pending, skipped, blocked, and human_needed items.
  • Codebase alignment: cross-references UAT items with project documentation to surface stale or missing verifications.
  • Practical planning: outputs a prioritized plan that guides manual testing and verification work.

Quick Start

Instruct the AI to run a cross-phase UAT audit against the current planning files to 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 generate a prioritized UAT audit plan across multiple project phases?▼

Generate a prioritized UAT audit plan by scanning .planning/phases/*/*-UAT.md and *-VERIFICATION.md files to consolidate pending, skipped, blocked, and human_needed items into a single manual test schedule.

How does cross-referencing UAT items with codebase documentation detect stale verification tasks?▼

Cross-referencing UAT items with codebase documentation detects stale verification tasks by matching planned test items against current project docs to identify missing or outdated validation requirements.

Can I run a cross-phase UAT audit without CLI access to core planning files?▼

No, running a cross-phase UAT audit requires CLI access to core planning files because the Skill must read .planning/phases directories to discover and consolidate outstanding verification items.

What is the best way to consolidate blocked and human_needed UAT items from separate phase files?▼

The best way to consolidate blocked and human_needed UAT items is scanning all phase UAT and verification markdown files to extract and elevate them into a unified prioritized testing workflow.

Why are some UAT items skipped during cross-phase verification audits?▼

UAT items are flagged as skipped during cross-phase verification audits when the scanning process identifies them in .planning/phases/*/*-UAT.md files but finds no corresponding completion or validation evidence in the codebase documentation.

What limitations exist when scanning .planning/phases markdown files for outstanding verification items?▼

The scanning limitation is that it strictly requires .planning/phases/*/*-UAT.md and *-VERIFICATION.md file formats to exist, meaning projects without this exact planning directory structure cannot be audited.

Related Skills

Explore More Software Engineering Skills→
aslaiiaslaii

gsd-audit-uat

Audit UAT and verification items across planning phases to produce a prioritized human test plan.

Community
Intermediate
coco-researchcoco-research
264

gsd-audit-uat

Audit UAT and verification items across planning phases against the codebase.

Community
Intermediate
GenproMMGenproMM

gsd-audit-uat

Automate cross-phase UAT audits and generate prioritized human test plans.

Official
Intermediate
tinner-deinnotinner-deinno

gsd-audit-uat

Identify outstanding UAT and verification items across planning phases.

Community
Intermediate