How do I install the 22 Game Release And Live Operations Runbook skill?

Run npx skillmds@latest add peterbamuhigire/22-game-release-and-live-operations-runbook 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 22 Game Release And Live Operations Runbook 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 22 Game Release And Live Operations Runbook?

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 22 Game Release And Live Operations Runbook free to use?

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

Who published 22 Game Release And Live Operations Runbook?

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

22 Game Release And Live Operations Runbook by peterbamuhigire

Name: 22 Game Release And Live Operations Runbook
Author: peterbamuhigire

22 Game Release And Live Operations Runbook

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.

File contents

Game Release and Live Operations Runbook

Use When

A tested game needs an operator-grade release, rollback, support or live-change procedure.

Do Not Use When

Current channel requirements or artefact identity are unavailable.
Do not rebuild after approval.

Required Inputs

Artefact	Source or provider	Required?	Behaviour when missing
Artefact, checksum, symbols, manifest, signing custody, channels and rollback	Build, QA and platform owners	Yes	Stop promotion.
Data/economy/ad config, privacy/child treatment, capacity, support and communications	Specialist owners	Conditional	Disable or block affected live scope.

Workflow

Verify dated official channel requirements and pinned versions.
Validate artefact, symbols, licences, checksum, provenance and signing boundary.
Rehearse install/upgrade, low storage, interruption, save migration, offline and credential failures.
Promote the tested artefact through cohorts with operational thresholds.
Define diagnosis, containment, rollback, communication and postmortem.
Gate config/events/economy/ad placements with schema, approval, audience/territory, expiry, wellbeing/trust thresholds, kill switch and reversal. Ads default off when consent, age treatment, creative review or SDK health is unknown.
Preserve no-ads/no-analytics degraded play where feasible and rehearse no-fill, offline, consent withdrawal, deletion, vendor outage and child-safe fallback.
Stop on missing rollback, symbols, privacy/rights approval or owner; recover by holding rollout or disabling affected live scope.

Outputs

Artefact	Consumer	Acceptance condition
Game release/liveops runbook	Release, operations and support	Artefact, steps, signals, owners, rollback and communications are executable.

Evidence Produced

Evidence	Reviewer	Acceptance condition
Promotion/rehearsal ledger	Release approver	Checksums, approvals, failures and rollback proof are retained.

Capability and permission boundaries

Read and search are allowed. Signing, submission, production config, messaging or rollback require authorised operators.

Degraded mode

Return a qualified dry run, mark unavailable checks not assessed, and keep promotion blocked.

Decision Rules

Choice or condition	Action	Failure or risk avoided
Checksum differs	Reject artefact.	Untested promotion.
Threshold breaches	Halt or roll back.	Expanded harm.
Live change mutates state	Simulate, version and rehearse reversal.	Corruption.

Quality Standards

Preserve symbols, checksums, manifests and rollback assets; minimise telemetry.

Anti-Patterns

Rebuild after QA. Fix: promote exact artifact.
Secrets in source. Fix: custody boundary.
Hotfix without migration. Fix: compatibility tests.
Event without expiry. Fix: kill switch and end state.
Reviews as telemetry. Fix: triangulate measured signals.
Ad incident handled only by vendor. Fix: retain studio kill switch, player support, evidence, containment and postmortem ownership.

References

Release manifest

---name: 22-game-release-and-live-operations-runbookdescription: 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.---# Game Release and Live Operations Runbook## Use When- A tested game needs an operator-grade release, rollback, support or live-change procedure.## Do Not Use When- Current channel requirements or artefact identity are unavailable.- Do not rebuild after approval.## Required Inputs| Artefact | Source or provider | Required? | Behaviour when missing ||---|---|---|---|| Artefact, checksum, symbols, manifest, signing custody, channels and rollback | Build, QA and platform owners | Yes | Stop promotion. || Data/economy/ad config, privacy/child treatment, capacity, support and communications | Specialist owners | Conditional | Disable or block affected live scope. |## Workflow1. Verify dated official channel requirements and pinned versions.2. Validate artefact, symbols, licences, checksum, provenance and signing boundary.3. Rehearse install/upgrade, low storage, interruption, save migration, offline and credential failures.4. Promote the tested artefact through cohorts with operational thresholds.5. Define diagnosis, containment, rollback, communication and postmortem.6. Gate config/events/economy/ad placements with schema, approval, audience/territory, expiry, wellbeing/trust thresholds, kill switch and reversal. Ads default off when consent, age treatment, creative review or SDK health is unknown.7. Preserve no-ads/no-analytics degraded play where feasible and rehearse no-fill, offline, consent withdrawal, deletion, vendor outage and child-safe fallback.8. Stop on missing rollback, symbols, privacy/rights approval or owner; recover by holding rollout or disabling affected live scope.## Outputs| Artefact | Consumer | Acceptance condition ||---|---|---|| Game release/liveops runbook | Release, operations and support | Artefact, steps, signals, owners, rollback and communications are executable. |## Evidence Produced| Evidence | Reviewer | Acceptance condition ||---|---|---|| Promotion/rehearsal ledger | Release approver | Checksums, approvals, failures and rollback proof are retained. |## Capability and permission boundariesRead and search are allowed. Signing, submission, production config, messaging or rollback require authorised operators.## Degraded modeReturn a qualified dry run, mark unavailable checks `not assessed`, and keep promotion blocked.## Decision Rules| Choice or condition | Action | Failure or risk avoided ||---|---|---|| Checksum differs | Reject artefact. | Untested promotion. || Threshold breaches | Halt or roll back. | Expanded harm. || Live change mutates state | Simulate, version and rehearse reversal. | Corruption. |## Quality Standards- Preserve symbols, checksums, manifests and rollback assets; minimise telemetry.## Anti-Patterns- Rebuild after QA. Fix: promote exact artifact.- Secrets in source. Fix: custody boundary.- Hotfix without migration. Fix: compatibility tests.- Event without expiry. Fix: kill switch and end state.- Reviews as telemetry. Fix: triangulate measured signals.- Ad incident handled only by vendor. Fix: retain studio kill switch, player support, evidence, containment and postmortem ownership.## References- [Release manifest](references/game-release-manifest.md)

Frequently asked questions