How do I install the 05 Game Technical Implementation Specification skill?

Run npx skillmds@latest add peterbamuhigire/05-game-technical-implementation-specification in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is 05 Game Technical Implementation Specification safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 05 Game Technical Implementation Specification?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is 05 Game Technical Implementation Specification free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published 05 Game Technical Implementation Specification?

peterbamuhigire (@peterbamuhigire) published this skill. Their other Agent Skills are listed on their SkillMD profile.

05 Game Technical Implementation Specification by peterbamuhigire

Name: 05 Game Technical Implementation Specification
Author: peterbamuhigire

05 Game Technical Implementation Specification

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.

peterbamuhigire fb73f2f 2 files · 4.5 KB Updated Sep 17, 2026

File contents

Game Technical Implementation Specification

Use When

Game architecture needs module, scene, data, asset, protocol, build and test seams.

Do Not Use When

Architecture or authority is undecided.
Do not copy legacy tutorial code without version verification.

Required Inputs

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.

Workflow

Decompose modules, scenes/worlds, data, assets and adapters with owners.
Define responsibilities, interfaces, events, lifetime and dependency rules.
Specify save/content/protocol versions, migrations, identifiers and idempotency.
Add engine-specific notes only for the pinned version.
Make every GIMPL-* consume GREQ-*, GARCH-*, relevant VCLAIM-*, approved game-design handoff, exact files/modules/assets or a bounded discovery task, and named exclusions.
Specify unit, integration, network, asset/UI, ad/privacy, accessibility/localisation, performance, security and device evidence per work package, including retained failed paths.
Define instrumentation purpose, errors, config, secrets, migrations, rollback/kill switches, owner role, estimate range/confidence and recalibration trigger.
Stop on an untestable interface, unresolved child/culture/privacy/ad decision or absent build target; recover with a spike and exit criteria.

Outputs

Artefact	Consumer	Acceptance condition
Game technical implementation specification	Client, backend, content, build and QA engineers	Packages have interfaces, versions, failures, tests and traces.

Evidence Produced

Evidence	Reviewer	Acceptance condition
`GIMPL-*` trace	Technical lead	Packages map requirements and architecture to code/assets, tests and build evidence.

Capability and permission boundaries

Read and search are allowed. Source edits, installs, services and releases require explicit authority.

Degraded mode

Return qualified interface stubs, mark validation not assessed, and do not claim buildability.

Decision Rules

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.

Quality Standards

No invented packages, hidden globals or placeholder methods; require failed-path evidence.

Anti-Patterns

Rules in scene components. Fix: isolate domain logic.
Singleton sprawl. Fix: scoped composition.
Manual import folklore. Fix: presets and validators.
Editor test as completion. Fix: packaged evidence.
Unbounded frame work. Fix: frequency budgets.
Visual handoff reduced to a screenshot. Fix: consume states, tokens, content, input/access rules and binary acceptance from the design engine.

References

Work-package schema

---name: 05-game-technical-implementation-specificationdescription: 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.---# Game Technical Implementation Specification## Use When- Game architecture needs module, scene, data, asset, protocol, build and test seams.## Do Not Use When- Architecture or authority is undecided.- Do not copy legacy tutorial code without version verification.## Required Inputs| 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. |## Workflow1. Decompose modules, scenes/worlds, data, assets and adapters with owners.2. Define responsibilities, interfaces, events, lifetime and dependency rules.3. Specify save/content/protocol versions, migrations, identifiers and idempotency.4. Add engine-specific notes only for the pinned version.5. Make every `GIMPL-*` consume `GREQ-*`, `GARCH-*`, relevant `VCLAIM-*`, approved game-design handoff, exact files/modules/assets or a bounded discovery task, and named exclusions.6. Specify unit, integration, network, asset/UI, ad/privacy, accessibility/localisation, performance, security and device evidence per work package, including retained failed paths.7. Define instrumentation purpose, errors, config, secrets, migrations, rollback/kill switches, owner role, estimate range/confidence and recalibration trigger.8. Stop on an untestable interface, unresolved child/culture/privacy/ad decision or absent build target; recover with a spike and exit criteria.## Outputs| Artefact | Consumer | Acceptance condition ||---|---|---|| Game technical implementation specification | Client, backend, content, build and QA engineers | Packages have interfaces, versions, failures, tests and traces. |## Evidence Produced| Evidence | Reviewer | Acceptance condition ||---|---|---|| `GIMPL-*` trace | Technical lead | Packages map requirements and architecture to code/assets, tests and build evidence. |## Capability and permission boundariesRead and search are allowed. Source edits, installs, services and releases require explicit authority.## Degraded modeReturn qualified interface stubs, mark validation `not assessed`, and do not claim buildability.## Decision Rules| 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. |## Quality Standards- No invented packages, hidden globals or placeholder methods; require failed-path evidence.## Anti-Patterns- Rules in scene components. Fix: isolate domain logic.- Singleton sprawl. Fix: scoped composition.- Manual import folklore. Fix: presets and validators.- Editor test as completion. Fix: packaged evidence.- Unbounded frame work. Fix: frequency budgets.- Visual handoff reduced to a screenshot. Fix: consume states, tokens, content, input/access rules and binary acceptance from the design engine.## References- [Work-package schema](references/game-work-package-schema.md)

Frequently asked questions