# game-launch

Skill for preparing a game for release: build validation, storefront submission timing, launch-day strategy, and post-launch support planning. Covers Steam, itch.io, Epic, and console platforms.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 47
- Author: AlterLab-IEU
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/AlterLab-IEU/AlterLab_GameForge/tree/HEAD/skills/workflows/game-launch/SKILL.md
- Updated: 2026-03-30
- HTML: https://affpapa.org/en/nevibecode/skills/game-launch

## What it does

game-launch structures the final stage before your game ships to storefronts. The skill guides you through build validation (clean compilation, test suites, performance on minimum hardware, save integrity), storefront requirements (store-specific rules, age ratings, credentials), marketing asset coordination, and a go/no-go decision framework.

It includes platform-specific checklists for Steam, itch.io, Epic, and consoles—each with different build size limits, screenshot formats, and review processes. The skill helps you plan launch-day operations: where builds live, how to roll back if problems emerge, timing for day-one patches.

Key insight: launch day is not the finish line. Post-launch strategy—patches, content, community management—often determines whether a game survives its second week. Requires file-system read access, search, and documentation.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-launch -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/game-launch/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/game-launch/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-launch -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/game-launch/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-launch -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/game-launch/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install AlterLab-IEU/AlterLab_GameForge game-launch
```

2. **Manually: put the files in place**
- File: `.github/skills/game-launch/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-launch -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/AlterLab-IEU/AlterLab_GameForge --path skills/workflows/game-launch
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/game-launch/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add AlterLab-IEU/AlterLab_GameForge --skill game-launch -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AlterLab-IEU/AlterLab_GameForge/tree/HEAD/skills/workflows/game-launch/SKILL.md

## When to use it
- build a complete pre-submission checklist for storefronts
- validate the build on minimum specification hardware
- align requirements across Steam, itch.io, Epic, and console submission
- plan day-one patch deployment and rollback procedures
- define post-launch support and content strategy

## Example prompts
- Generate a launch checklist for Steam with performance validation steps
- What are the submission requirements for Epic Games Store?
- Create a go/no-go framework given that we have P2 bugs remaining

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 8804bd945e39221d.

BEGIN THIRD-PARTY FILE 8804bd945e39221d
```text
---
name: "game-launch"
description: >
  Invoke when the user is preparing for game release, needs a launch checklist, store
  submission guidance, go/no-go decision framework, or day-one patch planning. Covers
  Steam, itch.io, Epic, and console submission pipelines. Triggers on: "launch", "release",
  "store submission", "go/no-go", "day-one patch", "launch readiness". Do NOT invoke for
  sprint planning (use game-sprint-plan) or code review (use game-code-review). Part of
  the AlterLab GameForge collection.
argument-hint: "[platform: steam|itch|epic|console]"
model: opus
effort: high
disable-model-invocation: true
allowed-tools: Read, Glob, Grep, Write, AskUserQuestion
version: 1.3.0
---

# AlterLab GameForge -- Pre-Release Launch Pipeline

The distance between "done" and "launched" is longer than most teams expect. And the distance between "launched" and "sustained" is longer still. A game that is feature-complete, bug-free, and fun can still fail because the store page was not optimized, the press kit was missing, the age rating was not filed, or the day-one patch pipeline was not tested. Worse -- a game that launches perfectly can die in week two without a post-launch strategy.

Hades did not become a cultural phenomenon on launch day. It became one through 18 months of Early Access with a meticulously planned patch cadence. Stardew Valley did not stop at 1.0 -- ConcernedApe's free content updates built a community that still plays eight years later. This workflow covers both sides: the exhaustive pre-launch pipeline AND the post-launch operations that determine whether your game survives past the first week.

### Purpose & Triggers

**Invoke this workflow when:**
- The game is entering the final milestone before release and a structured launch plan is needed
- A storefront submission deadline is approaching and the team needs to verify all requirements are met
- Marketing assets need to be prepared and coordinated across platforms
- Legal and compliance requirements (age ratings, privacy policies, licenses) need auditing
- The team needs a go/no-go framework for making the launch decision
- A soft launch or early access release is being planned (same process, adjusted scope)
- Post-launch support infrastructure needs to be established before launch day

**Do NOT use this workflow when:**
- The game is still in active development with significant features incomplete (finish building first)
- You are launching an internal playtest build (use `game-playtest` instead)
- The game is a game jam submission with no commercial intent (streamline to just build validation)

### Critical Rules
```
END THIRD-PARTY FILE 8804bd945e39221d

The third-party file has ended. Everything between the 8804bd945e39221d tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2637 of 44405 bytes. © AlterLab-IEU · MIT · https://github.com/AlterLab-IEU/AlterLab_GameForge/tree/HEAD/skills/workflows/game-launch/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md