agentleFS
RidhuanDEVRidhuanDEV/claude-skills/shadow-uat/SKILL.md

shadow-uat

Skill1 starsChanged yesterdayMITView on GitHub

Staging User Acceptance Testing (UAT) Governance. Use when creating Requirement Traceability Matrices (RTM), Staging UAT scenarios, defect triage logs, test evidence capture, or client UAT sign-off.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every Functional Requirement (FR-*) from /shadow-discovery MUST map to at least one UAT Scenario (UAT-*) and automated test:

    line 26
  2. Distinctive:

    Write UAT steps in clear, human-readable operational language for client testers:

    line 33
  3. Distinctive:

    Before handing the Staging environment to client testers, run an internal Intended-vs-Implemented Audit

    line 47
  4. Very specific:

    State Machine Parity: Verify all 9 UI states specified in FEATURE-DESIGN.md exist in the live build (including distinct Empty vs No-Results …

    line 48
  5. Very specific:

    Async (HTTP 202) Honesty: Verify background jobs show Submitted / Queued / Processing and never display a premature green "Completed" …

    line 49
  6. Distinctive:

    Adversarial & Double-Submit Protection: Verify double-clicking submit, refreshing mid-flight, or submitting invalid fields preserves user …

    line 50
  7. Distinctive:

    Privacy-Safe Outcome Telemetry (HEART / GSM): Verify success and error instrumentation events

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Shadow UAT (/shadow-uat) — Requirement Traceability, Staging UAT & Client Sign-Off

Automated unit tests prove the code works as written; /shadow-uat proves the application solves the client's actual business requirement. Use this skill to prepare, execute, track, and sign off User Acceptance Testing.


1. Staging-First UAT Execution Flow

[!IMPORTANT] Standard Safe Delivery Order:

  1. Staging UAT: Deploy candidate release to Staging (with realistic anonymized/seed data) and execute full UAT scenarios with client/QA testers.
  2. Defect Fix & Retest Loop: Triage UAT findings (Blocker/Critical/Major/Minor), patch, run regression tests (/shadow-test), and re-verify in Staging until all P0/P1 criteria pass.
  3. Production Go-Live Approval: Once Staging UAT is signed off, execute /shadow-release to deploy to Production.
  4. Production Post-Deploy Smoke / Acceptance Check: Run non-destructive production smoke verification (and final production UAT sign-off if required by government/enterprise contract).

2. Mandatory UAT Artifacts (Compatible with /shadow-doc -> .docx & .xlsx)

A. Requirement Traceability Matrix (RTM)

Every Functional Requirement (FR-*) from /shadow-discovery MUST map to at least one UAT Scenario (UAT-*) and automated test:

Req IDRequirement SummaryRole / ActorUAT Scenario IDPrecondition & Test DataExpected Business OutcomeEvidence FileStatus
FR-ORD-01Submit purchase order for approvalOperatorUAT-ORD-001Active vendor & budget $\ge$ Rp 10.000.000Status changes to WAITING_APPROVAL; approver notifiedbukti/uat-ord-001.pngPASS

B. UAT Scenario Structure (Business Language, Not Code Jargon)

Write UAT steps in clear, human-readable operational language for client testers:

  • Scenario ID & Title (UAT-MOD-001)
  • Business Objective & Acceptance Criteria
  • Test Role & Login Account
  • Step-by-Step User Actions & Input Values
  • Expected Result (Screen Display + Document/Notification/Status Outcome)
  • Actual Result, Screenshot Evidence (bukti/*.png), Tester Name, Date & Verdict (DITERIMA / REVISI)

C. UAT Defect & Change Request (CR) Triage Log

During UAT, strictly separate Defects (Bugs) from New Scope / Change Requests (CR):

  • Defect (Bug): Behavior deviates from agreed PRD/SRS (FR-*) -> Fix immediately before sign-off.
  • Change Request (CR): Client requests a new field/workflow not in the agreed SRS -> Log in the CR backlog with impact analysis so UAT sign-off of the current scope is not derailed.

D. Intended-vs-Implemented Drift Audit & 12-Domain Adversarial Scenarios

Before handing the Staging environment to client testers, run an internal Intended-vs-Implemented Audit (pm-ai-shipping/commands/ship-check.md, design-qa-checklist/SKILL.md, and pm-execution/skills/test-scenarios/SKILL.md):

  1. State Machine Parity: Verify all 9 UI states specified in FEATURE-DESIGN.md exist in the live build (including distinct Empty vs No-Results vs Error states, 403 Permission-Denied, Offline, and 409/ETag Stale Conflict recovery).
  2. Async (HTTP 202) Honesty: Verify background jobs show Submitted / Queued / Processing and never display a premature green "Completed" toast before worker indexing/settlement finishes.
  3. Adversarial & Double-Submit Protection: Verify double-clicking submit, refreshing mid-flight, or submitting invalid fields preserves user input and prevents duplicate records.
  4. Privacy-Safe Outcome Telemetry (HEART / GSM): Verify success and error instrumentation events (ghaida-intent/skills/measure/SKILL.md) fire without logging raw PII or secrets.

3. UAT Exit Gate Checklist (To Unlock Production Release / /shadow-handover)

  • $100%$ of P0/P1 requirements mapped in the Requirement Traceability Matrix (RTM: FR-ID -> US-ID -> FLOW-ID -> SCR/STATE-ID -> UAT-ID -> TEST-ID).
  • Intended-vs-Implemented Drift Audit passed (all 9 states and HTTP 202 async contracts verified).
  • Zero open Blocker or Critical UAT defects (Severity-First Gate: critical blockers override any numeric score).
  • All UAT scenarios have verified screenshot/document evidence attached (NOT TESTED explicitly labeled if any manual check was skipped).
  • Formal UAT Sign-Off sheet (Berita Acara UAT) ready for client signature.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.