Performs a cross-phase audit of UAT requirements, ensuring all verification tasks are tracked and addressed.

Install

mkdir -p .claude/skills/gsd-audit-uat-electroheadfx && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16571" && unzip -o skill.zip -d .claude/skills/gsd-audit-uat-electroheadfx && rm skill.zip

Installs to .claude/skills/gsd-audit-uat-electroheadfx

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Cross-phase audit of all outstanding UAT and verification items
63 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Scan all phases for pending UAT items
  • Scan all phases for skipped UAT items
  • Scan all phases for blocked UAT items
  • Scan all phases for human_needed UAT items
  • Cross-reference against codebase to detect stale documentation

How it works

This skill scans project phases for outstanding UAT and verification items, cross-references them with the codebase to find stale documentation, and then generates a prioritized human test plan.

Inputs & outputs

You give it
user text after $gsd-audit-uat
You get back
prioritized human test plan

When to use gsd-audit-uat

  • Auditing pending UAT items before a release
  • Verifying completion of project requirements
  • Tracking unresolved verification tasks

About this skill

<codex_skill_adapter>

A. Skill Invocation

  • This skill is invoked by mentioning $gsd-audit-uat.
  • Treat all user text after $gsd-audit-uat as {{GSD_ARGS}}.
  • If no arguments are present, treat {{GSD_ARGS}} as empty.

B. AskUserQuestion → request_user_input Mapping

GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:

Parameter mapping:

  • headerheader
  • questionquestion
  • Options formatted as "Label" — description{label: "Label", description: "description"}
  • Generate id from header: lowercase, replace spaces with underscores

Batched calls:

  • AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]

Multi-select workaround:

  • Codex has no multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.

Execute mode fallback:

  • When request_user_input is rejected or unavailable, you MUST stop and present the questions as a plain-text numbered list, then wait for the user's reply. Do NOT pick a default and continue (#3018).
  • You may only proceed without a user answer when one of these is true: (a) the invocation included an explicit non-interactive flag (--auto or --all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths).
  • Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.

C. Task() → spawn_agent Mapping

GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:

Direct mapping:

  • Task(subagent_type="X", prompt="Y")spawn_agent(agent_type="X", message="Y")
  • Task(model="...") → omit. spawn_agent has no inline model parameter; GSD embeds the resolved per-agent model directly into each agent's .toml at install time so model_overrides from .planning/config.json and ~/.gsd/defaults.json are honored automatically by Codex's agent router.
  • fork_context: false by default — GSD agents load their own context via <files_to_read> blocks
  • Task(isolation="worktree") / Agent(isolation="worktree") → no direct Codex mapping. Codex spawn_agent does not create or bind a git worktree automatically. Workflows that require this isolation must fail closed or use an explicit manual worktree protocol before spawning (#3360).

Spawn restriction:

  • Codex restricts spawn_agent to cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.

Parallel fan-out:

  • Spawn multiple agents → collect agent IDs → wait(ids) for all to complete

Result parsing:

  • Look for structured markers in agent output: CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
  • close_agent(id) after collecting results from each agent </codex_skill_adapter>
<objective> Scan all phases for pending, skipped, blocked, and human_needed UAT items. Cross-reference against codebase to detect stale documentation. Produce prioritized human test plan. </objective>

<execution_context> @/Users/lmarques/Dev/efx-mux/.codex/get-shit-done/workflows/audit-uat.md </execution_context>

<context> Core planning files are loaded in-workflow via CLI.

Scope: Glob: .planning/phases//-UAT.md Glob: .planning/phases//-VERIFICATION.md </context>

When not to use it

  • When automatic spawning of sub-agents is not permitted
  • When a git worktree is required for isolation and not explicitly handled

Limitations

  • Codex restricts spawn_agent to cases where the user has explicitly requested sub-agents.

How it compares

This skill automates the cross-phase audit and test plan generation, unlike a manual process that would require individual checks and compilation.

Compared to similar skills

gsd-audit-uat side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
gsd-audit-uat (this skill)03moNo flagsIntermediate
tpp06moNo flagsIntermediate
do-plan01moNo flagsAdvanced
acceptance-criteria04moNo flagsBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry