launch-checklist

Scan game repositories and compile a markdown launch readiness checklist.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill launch-checklist-euraika-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launch-checklist
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/launch-checklist
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill launch-checklist-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a structured, end-to-end readiness audit that surfaces blocking and conditional items across engineering, content, QA, store, marketing, community, infrastructure, and legal so teams can make a clear go/no-go decision before launch.

Core Features & Use Cases

  • Automated repository scans that count TODO/FIXME/HACK markers, detect debug output and hardcoded test values, and verify build and test health.
  • Context-aware aggregation that reads AGENTS.md, production milestones, existing release checklists, and content calendars to compile a cross-department checklist.
  • Decision workflow integration that summarizes total items, identifies blockers and conditional risks, prompts before writing release artifacts, and links to follow-up commands like gate-check and team-release.
  • Dry-run and save options enabling non-destructive preview or consented writing of production/releases/launch-checklist-[date].md.

Quick Start

Use $launch-checklist with a launch date or dry-run to generate a complete launch readiness checklist and summary.

Frequently Asked Questions about launch-checklist

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

FAQPage Schema
How do I generate a comprehensive game launch readiness checklist?

Generate a comprehensive launch readiness checklist by scanning your game repository to count TODO/FIXME/HACK markers, detect debug artifacts, and aggregate cross-department items from project artifacts like AGENTS.md into a single markdown file.

What is included in a pre-release sign-off audit for a game?

A pre-release sign-off audit covers technical, content, QA, store, marketing, community, infrastructure, and legal items, summarizing total blockers and conditional risks to facilitate a clear go/no-go decision before launch.

How do I detect hardcoded test values and debug output before a release?

Detect hardcoded test values and debug output by running automated repository scans that inspect code health, count TODO/FIXME/HACK occurrences, and flag debug artifacts for pre-release review.

Can I preview a launch checklist without writing files to my repository?

Yes, you can preview a launch checklist without writing files by using a dry-run option to non-destructively generate and review the release validation output before consenting to write the markdown file.

How do I compile cross-department release checklists from existing project artifacts?

Compile cross-department release checklists by contextually reading existing project artifacts like AGENTS.md, production milestones, and content calendars, then aggregating engineering, QA, and marketing items into a unified pre-release review.

What are the limitations of automated launch readiness validation for game repositories?

Automated launch readiness validation is limited to scanning code health and aggregating documented project artifacts, meaning it cannot assess undocumented risks or replace manual review of subjective legal and marketing readiness.