メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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 planning game QA, playtesting, balance, deterministic simulation, save migration, multiplayer network conditions, device performance, accessibility, localisation, security, certification, and release-candidate evidence.
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.
SOC 職業分類に基づく
| name | 05-game-technical-implementation-specification |
| description | 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. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
GREQ-*, GARCH-*, ADRs, toolchain locks and acceptance tests | Architecture, engineering and QA | Yes | Stop the work package and return missing contracts. |
| Asset/UI handoff, data/ads/privacy schemas, adapters, protocol and build interface | Design and specialist owners | Conditional | Exclude or mark integration blocked. |
GIMPL-* consume GREQ-*, GARCH-*, relevant VCLAIM-*, approved game-design handoff, exact files/modules/assets or a bounded discovery task, and named exclusions.| Artefact | Consumer | Acceptance condition |
|---|---|---|
| Game technical implementation specification | Client, backend, content, build and QA engineers | Packages have interfaces, versions, failures, tests and traces. |
| Evidence | Reviewer | Acceptance condition |
|---|---|---|
GIMPL-* trace | Technical lead | Packages map requirements and architecture to code/assets, tests and build evidence. |
Read and search are allowed. Source edits, installs, services and releases require explicit authority.
Return qualified interface stubs, mark validation not assessed, and do not claim buildability.
| Choice or condition | Action | Failure or risk avoided |
|---|---|---|
| Pure logic uses engine objects | Invert dependency. | Fragile tests. |
| Import is manual | Define presets and validation. | Content drift. |
| Schema is incompatible | Add migration or recovery rejection. | Stranded state. |