원클릭으로 Manus에서 모든 스킬 실행

uat-plan

스타4

포크0

업데이트2026년 4월 24일 00:08

"Use when designing a User Acceptance Test plan, defining exit criteria, or coordinating business sign-off. Triggers on "UAT", "user acceptance", "business validation", "sign-off", "go/no-go"."

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

paulasilvatech

paulasilvatech/workshop-datacorp-team-kit

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

UAT Plan

When to invoke

"Design a UAT plan for the release."
"What are sensible exit criteria for UAT?"
"Create a UAT schedule with business users."

UAT vs. other testing

Testing	Who	Goal
Unit / integration	Engineers	Code correctness
System / E2E	QA	System behaviour
UAT	Business users	"Does this solve the real business problem?"

UAT validates fit for purpose, not defects. Defects found here signal failure in earlier gates.

Steps

Identify business scenarios (not test cases). Group by workflow, role, frequency. Aim for 20-40 scenarios for a medium release.
Select testers: real end users, not proxies. Cover each role in scope.
Prepare environment: UAT-specific env with sanitised prod-like data. Reset between sessions.
Write scenarios in business language. No IDs, no SQL, no screenshots from test tooling.
Schedule: 2-4 hour sessions, morning is better, 3-5 scenarios per session per tester.
Capture results: PASS / PASS with notes / FAIL / BLOCKED. Every FAIL needs a reproduction trace.
Daily triage: defects classified P1/P2/P3 within 24h.
Exit gate: meet defined criteria before signing off.

Exit criteria (example)

100% of P0 and P1 scenarios executed.
0 open P1 defects.
P2 defects with mitigation or deferred with business approval.
Business sponsor signs the UAT report.

Output template

## UAT Plan - <Release>

### Scope
In: <modules>
Out: <modules>

### Scenarios
| ID | Role | Scenario | Priority | Expected outcome | Tester | Result | Notes |
|----|------|----------|----------|------------------|--------|--------|-------|
| UAT-01 | Tax Agent | Assess a taxpayer with penalty | P0 | Penalty calculated per rule R14 | Maria | PASS | |
| UAT-02 | Tax Agent | Reverse an assessment | P0 | Original status restored, audit trail | Maria | FAIL | Audit trail missing user id |

### Schedule
| Date | Session | Testers | Scenarios |
|------|---------|---------|-----------|
| 2026-04-28 AM | 1 | Maria, Joao | UAT-01-05 |

### Exit criteria
- [ ] 100% P0 executed
- [ ] 0 open P1
- [ ] Business sign-off

### Sign-off
<business sponsor>, <date>

Anti-patterns

Engineers playing UAT tester.
Scenarios written in QA case format (steps/expected/actual in technical language).
No environment reset - tests contaminate each other.
UAT used to discover functional defects (means earlier testing failed).

Quality gate

Reject UAT kickoff if scenarios are not in business language or testers are not real end users.

이 저장소의 다른 Skills

같은 저장소

ears-validation

paulasilvatech/workshop-datacorp-team-kit

"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."

2026-05-184

capability-map

paulasilvatech/workshop-datacorp-team-kit

"Use when mapping business capabilities, identifying overlap or gaps across the enterprise, or aligning IT investments to business outcomes. Triggers on "capability map", "business capability", "domain map", "enterprise architecture"."

2026-05-184

adr-drafting

paulasilvatech/workshop-datacorp-team-kit

"Use when drafting Architecture Decision Records, evaluating alternatives, or documenting technical trade-offs. Triggers on "ADR", "architecture decision", "trade-off", "pick between", "why did we choose"."

2026-05-184

context-audit

paulasilvatech/workshop-datacorp-team-kit

"Use when a new engineer joins the team, when onboarding to an unfamiliar codebase, or when auditing whether the team has shared understanding. Triggers on "onboard", "context", "knowledge gap", "bus factor", "team understanding"."

2026-05-184

refactor-safely

paulasilvatech/workshop-datacorp-team-kit

Use when refactoring legacy code, extracting a service, or making behavior-preserving changes. Triggers on 'refactor', 'legacy code', 'strangler fig', 'characterization test', 'mikado method'.

2026-05-184

tdd-workflow

paulasilvatech/workshop-datacorp-team-kit

Use when practicing test-driven development, writing a failing test first, or coaching red-green-refactor. Triggers on 'TDD', 'red-green-refactor', 'test first', 'failing test', 'write a test'.

2026-05-184

name	UAT Plan
description	"Use when designing a User Acceptance Test plan, defining exit criteria, or coordinating business sign-off. Triggers on "UAT", "user acceptance", "business validation", "sign-off", "go/no-go"."

UAT Plan

When to invoke

"Design a UAT plan for the release."
"What are sensible exit criteria for UAT?"
"Create a UAT schedule with business users."

UAT vs. other testing

Testing	Who	Goal
Unit / integration	Engineers	Code correctness
System / E2E	QA	System behaviour
UAT	Business users	"Does this solve the real business problem?"

UAT validates fit for purpose, not defects. Defects found here signal failure in earlier gates.

Steps

Identify business scenarios (not test cases). Group by workflow, role, frequency. Aim for 20-40 scenarios for a medium release.
Select testers: real end users, not proxies. Cover each role in scope.
Prepare environment: UAT-specific env with sanitised prod-like data. Reset between sessions.
Write scenarios in business language. No IDs, no SQL, no screenshots from test tooling.
Schedule: 2-4 hour sessions, morning is better, 3-5 scenarios per session per tester.
Capture results: PASS / PASS with notes / FAIL / BLOCKED. Every FAIL needs a reproduction trace.
Daily triage: defects classified P1/P2/P3 within 24h.
Exit gate: meet defined criteria before signing off.

Exit criteria (example)

100% of P0 and P1 scenarios executed.
0 open P1 defects.
P2 defects with mitigation or deferred with business approval.
Business sponsor signs the UAT report.

Output template

## UAT Plan - <Release>

### Scope
In: <modules>
Out: <modules>

### Scenarios
| ID | Role | Scenario | Priority | Expected outcome | Tester | Result | Notes |
|----|------|----------|----------|------------------|--------|--------|-------|
| UAT-01 | Tax Agent | Assess a taxpayer with penalty | P0 | Penalty calculated per rule R14 | Maria | PASS | |
| UAT-02 | Tax Agent | Reverse an assessment | P0 | Original status restored, audit trail | Maria | FAIL | Audit trail missing user id |

### Schedule
| Date | Session | Testers | Scenarios |
|------|---------|---------|-----------|
| 2026-04-28 AM | 1 | Maria, Joao | UAT-01-05 |

### Exit criteria
- [ ] 100% P0 executed
- [ ] 0 open P1
- [ ] Business sign-off

### Sign-off
<business sponsor>, <date>

Anti-patterns

Engineers playing UAT tester.
Scenarios written in QA case format (steps/expected/actual in technical language).
No environment reset - tests contaminate each other.
UAT used to discover functional defects (means earlier testing failed).

Quality gate

Reject UAT kickoff if scenarios are not in business language or testers are not real end users.