
Gsd Audit Uat
- 1 installs
- 1 repo stars
- Updated May 10, 2026
- aesir-tecnologia/folhario
gsd-audit-uat is a Claude Code skill that cross-phase audits all outstanding UAT and verification items and produces a prioritized human test plan.
About
gsd-audit-uat is a Claude Code skill from the GSD (get-shit-done) workflow system that audits outstanding user-acceptance-testing and verification items across all project phases. It globs the .planning phase UAT and VERIFICATION files, cross-references them against the codebase to flag stale docs, and produces a prioritized human test plan. It also maps Claude Code workflow primitives (AskUserQuestion, Task) onto Codex equivalents so the same audit runs under Codex.
- Scans all project phases for pending, skipped, blocked, and human-needed UAT items
- Cross-references UAT docs against the codebase to catch stale documentation
- Adapts Claude Code GSD workflow syntax to run under the Codex agent runtime
Gsd Audit Uat by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,750 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
gsd-audit-uat capabilities & compatibility
- Capabilities
- uat audit · test planning · verification tracking
- Use cases
- testing
What gsd-audit-uat says it does
Cross-phase audit of all outstanding UAT and verification items
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.
npx skills add https://github.com/aesir-tecnologia/folhario --skill gsd-audit-uatAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 1 |
| Last updated | May 10, 2026 |
| Repository | aesir-tecnologia/folhario ↗ |
What it does
Audit every outstanding UAT and verification item across project phases and produce a prioritized human test plan.
When should I use this skill?
You want a single pass over all project phases to find pending, skipped, blocked, or human-needed UAT items before release.
What you get
A prioritized human test plan covering all pending, skipped, blocked, and human-needed UAT items with stale docs flagged.
- Prioritized human test plan of outstanding UAT and verification items
By the numbers
- Globs 2 file patterns (*-UAT.md and *-VERIFICATION.md) across all phases
- Classifies items into 4 states (pending, skipped, blocked, human_needed)
Files
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-audit-uat. - Treat all user text after
$gsd-audit-uatas{{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:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
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_inputis 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_agenthas no inlinemodelparameter;
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: falseby default — GSD agents load their own context via<files_to_read>blocks
Spawn restriction:
- Codex restricts
spawn_agentto 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/machado/Projects/folhario/.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>