What problem does it solve? Launching a game requires coordinating code, content, QA, store, legal, infrastructure, and marketing readiness, and teams often miss critical items scattered across departments. This Skill consolidates every launch requirement into one structured checklist with a go/no-go decision framework. ## Core Features & Use Cases - Codebase Health Scan: Counts TODO, FIXME, and HACK comments, detects leftover debug output, placeholder assets, and hardcoded dev values before launch. - Full-Department Checklist: Generates a Markdown checklist covering code readiness, content, QA, store pages, legal, infrastructure, community, marketing, and operations. - Go/No-Go Sign-Offs: Produces blocking and conditional item summaries plus sign-off slots for Creative Director, Technical Director, QA Lead, Producer, and Release Manager. - Use Case: Two weeks before shipping your game, run a dry-run to surface 12 unresolved FIXMEs and missing store screenshots, then regenerate the final checklist on launch day for formal sign-off. ## Quick Start Ask the assistant to run /launch-checklist with your target launch date, or use dry-run mode to preview the checklist without creating sign-off entries.
