ferrox-audit-uat

Gather unresolved UAT verification items into a prioritized review list.

21|9|Updated Jul 21, 2026
One-click install
npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-audit-uat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ferrox-audit-uat
Source: https://github.com/FerroxLabs/ferrox-factory/tree/main/skills/ferrox-audit-uat
Command: npx skills add https://github.com/FerroxLabs/ferrox-factory --skill ferrox-audit-uat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you collect and prioritize all unresolved verification issues so nothing slips through the final testing and approval stages.

Core Features & Use Cases

  • UAT Issue Gathering: Scans phase files for pending, skipped, blocked, and human_needed items.
  • Cross-Reference Review: Compares verification notes against the codebase to surface stale or inconsistent documentation.
  • Prioritized Test Planning: Produces a human-focused test plan that highlights the most important follow-up items first.

Quick Start

Ask the skill to scan the project for all open UAT verification items and produce a prioritized human test plan.

Frequently Asked Questions about ferrox-audit-uat

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

FAQPage Schema
How do I gather unresolved UAT verification items across project phases?

Scan your phase markdown files and cross-reference codebase evidence to identify pending, skipped, blocked, and human-needed UAT verification items, consolidating them into a single prioritized review list.

What is a UAT blocker audit in planning-driven software delivery?

A UAT blocker audit is the process of collecting and prioritizing unresolved verification issues by comparing documentation against the codebase, ensuring nothing slips through final testing and approval stages.

How do I cross-reference verification notes against the codebase to find stale documentation?

Cross-reference verification notes against the codebase during a phase audit to surface stale or inconsistent documentation, filtering for pending, skipped, blocked, and human_needed tracking items.

Can I generate a prioritized human test plan from open verification items?

Yes, you can produce a human-focused test plan that highlights the most important follow-up items first by scanning project phase files for all open UAT verification items.

Does this UAT audit approach work without external dependencies?

Yes, this UAT audit approach operates without external dependencies, scanning phase markdown files and codebase evidence directly to track verification consistency.

What's the best way to track blocked and skipped verification items in phase audits?

Scan phase files for blocked and skipped statuses, cross-reference them with codebase evidence, and consolidate them into a prioritized review list for tracking verification items.