メニュー
"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 ページを確認してインストールできます。
SOC 職業分類に基づく
"Use when validating requirements against EARS notation patterns. Triggers on "EARS", "requirement review", "requirement quality", "shall statement", "REQ-ID"."
"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"."
"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"."
"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"."
Use when refactoring legacy code, extracting a service, or making behavior-preserving changes. Triggers on 'refactor', 'legacy code', 'strangler fig', 'characterization test', 'mikado method'.
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'.
| 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"." |
| 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.
## 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>
Reject UAT kickoff if scenarios are not in business language or testers are not real end users.