메뉴
Use when planning game QA, playtesting, balance, deterministic simulation, save migration, multiplayer network conditions, device performance, accessibility, localisation, security, certification, and release-candidate evidence.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when defining a game's player promise, product hypotheses, platform options, production model, vertical-slice evidence, commercial boundaries, or greenlight decision before detailed requirements.
Use when specifying testable game software requirements for player experience, gameplay state, platforms, multiplayer, saves, content, performance, accessibility, telemetry, security, builds, release, or live operations.
Use when designing game client, authoritative state, engine integration, content, saves, multiplayer backend, platform adapters, telemetry, security, build, and live-operations architecture from an approved game SRS.
Use when turning approved game requirements and architecture into implementable Unity, Godot, Unreal, Apple-native, multiplayer, content-pipeline, build, and telemetry work packages with code and asset contracts.
Use when documenting reproducible game builds, signing, artifact promotion, distribution, staged rollout, rollback, crash diagnosis, matchmaking operations, live events, remote config, economy controls, support, or incidents.
Use when assembling or reviewing game greenlight, milestone, release, rights, security, player-research, build, test, live-operations, and independent-replication evidence without inflating capability claims.
| name | 09-game-test-and-player-evidence-plan |
| description | Use when planning game QA, playtesting, balance, deterministic simulation, save migration, multiplayer network conditions, device performance, accessibility, localisation, security, certification, and release-candidate evidence. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
01-test-strategy.| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| Requirements, architecture, build manifest, targets and gates | Product, engineering, QA and release | Yes | Stop and issue a readiness gap. |
| Research, learning, culture, wellbeing, ads/privacy, network, accessibility, localisation and threat cases | Specialist owners | Conditional | Mark coverage not assessed. |
| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Game test and player evidence plan | QA, design, engineering and release | Cases map to requirements, environments, oracles, evidence and decisions. |
| Evidence | Reviewer | Acceptance condition |
|---|---|---|
GTEST-* matrix | QA reviewer | Build, device, scene, seed, network and outcome are reproducible. |
Read and search are allowed; planning is read-only. Shared-service, player-data or security tests require authority and consent.
Return the narrowest qualified plan, mark unavailable checks not assessed, and retain blocked gates.
| Choice or condition | Action | Failure or risk avoided |
|---|---|---|
| Oracle absent | Redesign or classify exploratory. | False confidence. |
| Capture lacks identity | Reject release evidence. | Irreproducibility. |
| Core accessibility blocker | Block or approve explicit exclusion. | Menu-only claims. |