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.
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-supplychainSkill
- shadow-testSkill
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
- Very specific: line 26
Every Functional Requirement (FR-*) from /shadow-discovery MUST map to at least one UAT Scenario (UAT-*) and automated test:
- Distinctive: line 33
Write UAT steps in clear, human-readable operational language for client testers:
- Distinctive: line 47
Before handing the Staging environment to client testers, run an internal Intended-vs-Implemented Audit
- Very specific: line 48
State Machine Parity: Verify all 9 UI states specified in FEATURE-DESIGN.md exist in the live build (including distinct Empty vs No-Results …
- Very specific: line 49
Async (
HTTP 202) Honesty: Verify background jobs show Submitted / Queued / Processing and never display a premature green "Completed" … - Distinctive: line 50
Adversarial & Double-Submit Protection: Verify double-clicking submit, refreshing mid-flight, or submitting invalid fields preserves user …
- Distinctive: line 51
Privacy-Safe Outcome Telemetry (HEART / GSM): Verify success and error instrumentation events
≈ “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.
Files
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:
- Staging UAT: Deploy candidate release to Staging (with realistic anonymized/seed data) and execute full UAT scenarios with client/QA testers.
- 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.- Production Go-Live Approval: Once Staging UAT is signed off, execute
/shadow-releaseto deploy to Production.- 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 ID | Requirement Summary | Role / Actor | UAT Scenario ID | Precondition & Test Data | Expected Business Outcome | Evidence File | Status |
FR-ORD-01 | Submit purchase order for approval | Operator | UAT-ORD-001 | Active vendor & budget $\ge$ Rp 10.000.000 | Status changes to WAITING_APPROVAL; approver notified | bukti/uat-ord-001.png | PASS |
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):
- State Machine Parity: Verify all 9 UI states specified in
FEATURE-DESIGN.mdexist in the live build (including distinct Empty vs No-Results vs Error states,403Permission-Denied, Offline, and409/ETagStale Conflict recovery). - Async (
HTTP 202) Honesty: Verify background jobs showSubmitted / Queued / Processingand never display a premature green"Completed"toast before worker indexing/settlement finishes. - Adversarial & Double-Submit Protection: Verify double-clicking submit, refreshing mid-flight, or submitting invalid fields preserves user input and prevents duplicate records.
- 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 202async contracts verified). - Zero open
BlockerorCriticalUAT defects (Severity-First Gate: critical blockers override any numeric score). - All UAT scenarios have verified screenshot/document evidence attached (
NOT TESTEDexplicitly labeled if any manual check was skipped). - Formal UAT Sign-Off sheet (
Berita Acara UAT) ready for client signature.
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
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.

