agentsclimarketplace
Sign in

Uat

Skill brandtam/skills/skills/uat

Run a user acceptance testing session with collect-grill-PRD workflow. Use when user says "uat", "start uat", "acceptance testing", "let's test", or invokes /uat. Captures observations as checklist items, grills for decisions, then generates a PRD.From its SKILL.md

Install
npx -y skills add brandtam/skills --skill uat

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.9 KB, 619 tokens by cl100k_base, as published. Nobody here has run it

UAT

User acceptance testing in three phases: collect, grill, PRD.

Phase 1: Collect

When the user starts a UAT round:

  1. Determine the round number by checking for existing local-docs/uat-round-*.md files
  2. Create local-docs/uat-round-N.md with a # UAT Round N heading
  3. Ensure local-docs/uat-screenshots/ exists
  4. Tell the user you're ready and to start dropping observations

While collecting:

  • The user drops observations one at a time — voice transcriptions, typed notes, screenshots, or images
  • Add each as a - [ ] checkbox item to the UAT doc
  • Keep descriptions concise but capture the full intent
  • If a screenshot is provided, save a reference to its path next to the item
  • Don't ask clarifying questions yet — just log and confirm. Say "Logged. Next." or similar
  • Stay in collect mode until the user says they're done ("done", "that's it", "finished testing", etc.)

Phase 2: Grill

When the user signals they're done collecting:

  1. Read back the full UAT document
  2. Walk through each item one at a time, asking targeted questions to resolve:
    • What specifically should change?
    • Are there sub-decisions (behavior, styling, scope)?
    • What's the recommended approach?
  3. Use AskUserQuestion for structured choices where appropriate
  4. After each item is resolved, update the UAT doc with sub-bullets capturing the decisions
  5. Present a summary table of all decisions when done

Phase 3: PRD

After grilling is complete:

  1. Write a PRD to local-docs/prd-uat-round-N.md covering:
    • Problem Statement
    • Solution
    • User Stories (extensive numbered list)
    • Implementation Decisions (modules to build/modify with specifics)
    • Testing Decisions
    • Out of Scope
    • Further Notes
  2. Survey the codebase to write informed implementation decisions — include module names and architectural patterns, not file paths (those rot)

Visual QA (optional)

When the user asks to verify changes visually, or after implementation:

  1. Write a Playwright script to screenshot each changed feature
  2. Save screenshots to local-docs/uat-screenshots/
  3. Review each screenshot and report findings
  4. Clean up the QA script after

Tips

  • Screenshots from the user are ephemeral in chat — note what they show but don't depend on accessing them later
  • The user may use voice transcription, so observations may be conversational. Extract the intent
  • Some items may be quick fixes, others may be architectural. Log them all the same way during collect
  • During grill, recommend an answer for each question so the user can just confirm or redirect

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most test skills give in 619 tokens

Counted across 1,201 of the 2,096 authors here whose files we hold, read 2026-09-06

  • Write a failing test before writing codein 43 of 1201, across 36 files
  • Run the full test suitein 36 of 1201, across 35 files
  • Test only one variable per experimentin 34 of 1201, across 17 files
  • Read product marketing context before asking questionsin 34 of 1201, across 14 files
  • Mock external dependenciesin 34 of 1201, across 30 files
  • Define primary, secondary, and guardrail metricsin 33 of 1201, across 16 files
  • Pre-determine sample size before startingin 31 of 1201, across 14 files
  • Test behavior rather than implementationin 31 of 1201, across 29 files
  • Formulate a hypothesis before designing a testin 30 of 1201, across 13 files
  • Document every test hypothesis, variant, and resultin 29 of 1201, across 11 files
  • Use descriptive test function namesin 25 of 1201, across 21 files
  • Commit to the methodology without stopping earlyin 24 of 1201, across 8 files

Said here and by no other author read

  • Determine the current UAT round number
  • Create a UAT round markdown file
  • Log user observations as checklist items
  • Confirm each observation without asking questions
  • Read back the UAT document when finished
  • Ask targeted questions for each item

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.