steam-launch-ops

Create a Steam launch operations runbook with release timing and go-live checks.

14|1|Updated Apr 12, 2026

Search Tags:#automation #release #operations #runbook #launch #steam

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill steam-launch-ops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: steam-launch-ops
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/steam-launch-ops
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill steam-launch-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams need a concise, actionable runbook that captures all release unlock timing, go‑live checks, on‑call ownership, monitoring, escalation thresholds, and hot‑fix triggers before a Steam launch.

Core Features & Use Cases

Context Aggregation: Reads the latest Steam publish plan, optional review readiness, pricing bundles, and the launch‑ops template.
Runbook Generation: Produces a complete launch operations document covering timing, owners, checks, monitoring, and hot‑fix criteria.
Safe Persistence: Asks for confirmation before writing the artifact to the repository and points to next‑step skills for coordination.

Quick Start

Request the steam‑launch‑ops skill to create a launch runbook for the upcoming Steam release.

Frequently Asked Questions about steam-launch-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a Steam launch runbook for release operations?▼

A Steam launch runbook consolidates production release plans, pricing bundles, and the launch-ops template into a single actionable artifact defining release unlock timing, go-live checks, and hot-fix triggers. It requires access to existing repository production files.

What should a Steam release operations document include for go-live checks?▼

A Steam release operations document should include release unlock timing, go-live checks, on-call ownership, monitoring, escalation thresholds, and hot-fix triggers. These components ensure a concise, actionable launch process for the team.

Do I need production release plans to generate a Steam launch runbook?▼

Yes, you need access to production release plans, pricing bundles, and the Steam launch operations template within the repository. The runbook is generated by aggregating these existing production and documentation files into one document.

Can I review a Steam launch runbook before it is saved to the repository?▼

Yes, the runbook generation process asks for confirmation before writing the artifact to the repository. This safe persistence step ensures you can review the completed launch operations document before it is committed.

What's the best way to define on-call ownership and escalation thresholds for a Steam launch?▼

The best way to define on-call ownership and escalation thresholds is using a dedicated launch operations runbook. It consolidates monitoring criteria and hot-fix triggers into a single actionable artifact prepared for the Steam release.

Why does my Steam launch runbook need hot-fix triggers and monitoring criteria?▼

Hot-fix triggers and monitoring criteria are needed in a Steam launch runbook to provide actionable escalation thresholds and ensure on-call ownership during the go-live process. This prevents unmanaged release operations failures.