launch-checklist
The launch-checklist skill provides a comprehensive pre-release validation system that scans a game project across eight departments (code, content, store, marketing, community, infrastructure, legal) and generates sign-off documentation. Invoke it explicitly with `/launch-checklist` when preparing a game for release. The skill audits code health by counting debug artifacts and analyzing build integrity, validates content assets against final standards, verifies platform compliance, and produces a detailed checklist with go/no-go determinations. Use this before submitting to app stores or launching live servers to ensure all departments have cleared critical launch requirements.
git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios /tmp/launch-checklist && cp -r /tmp/launch-checklist/.claude/skills/launch-checklist ~/.claude/skills/launch-checklistSKILL.md
> **Explicit invocation only**: This skill should only run when the user explicitly requests it with `/launch-checklist`. Do not auto-invoke based on context matching. ## Phase 1: Parse Arguments Read the argument for the launch date or `dry-run` mode. Dry-run mode generates the checklist without creating sign-off entries or writing files. --- ## Phase 2: Gather Project Context - Read `CLAUDE.md` for tech stack, target platforms, and team structure - Read the latest milestone in `production/milestones/` - Read any existing release checklist in `production/releases/` - Read the content calendar in `design/live-ops/content-calendar.md` if it exists --- ## Phase 3: Scan Codebase Health - Count `TODO`, `FIXME`, `HACK` comments and their locations - Check for any `console.log`, `print()`, or debug output left in production code - Check for placeholder assets (search for `placeholder`, `temp_`, `WIP_`) - Check for hardcoded test/dev values (localhost, test credentials, debug flags) --- ## Phase 4: Generate the Launch Checklist ```markdown # Launch Checklist: [Game Title] Target Launch: [Date or DRY RUN] Generated: [Date] --- ## 1. Code Readiness ### Build Health - [ ] Clean build on all target platforms - [ ] Zero compiler warnings - [ ] All unit tests passing - [ ] All integration tests passing - [ ] Performance benchmarks within targets - [ ] No memory leaks (verified via extended soak test) - [ ] Build size within platform limits - [ ] Build version correctly set and tagged in source control ### Code Quality - [ ] TODO count: [N] (zero required for launch, or documented exceptions) - [ ] FIXME count: [N] (zero required) - [ ] HACK count: [N] (each must have documented justification) - [ ] No debug output in production code - [ ] No hardcoded dev/test values - [ ] All feature flags set to production values - [ ] Error handling covers all critical paths - [ ] Crash reporting integrated and verified ### Security - [ ] No exposed API keys or credentials in source - [ ] Save data encrypted - [ ] Network communication secured (TLS/DTLS) - [ ] Anti-cheat measures active (if multiplayer) - [ ] Input validation on all server endpoints (if multiplayer) - [ ] Privacy policy compliance verified --- ## 2. Content Readiness ### Assets - [ ] All placeholder art replaced with final assets - [ ] All placeholder audio replaced with final audio - [ ] Audio mix finalized and approved by audio director - [ ] All VFX polished and performance-verified - [ ] No missing or broken asset references - [ ] Asset naming conventions enforced ### Text and Localization - [ ] All player-facing text proofread - [ ] No hardcoded strings (all externalized for localization) - [ ] All supported languages translated and verified - [ ] Text fits UI in all languages (text fitting pass complete) - [ ] Font coverage verified for all supported languages - [ ] Credits complete, accurate, and up to date ### Game Content - [ ] All levels/maps playable from start to finish - [ ] Tutorial flow complete and tested with new players - [ ] All achievements/trophies implemented and tested - [ ] Save/load works correctly for all game states - [ ] Difficulty settings balanced and tested - [ ] End-game/credits sequence complete --- ## 3. Quality Assurance ### Testing - [ ] Full regression test suite passed - [ ] Zero S1 (Critical) bugs open - [ ] Zero S2 (Major) bugs open (or documented exceptions) - [ ] Soak test passed (8+ hours continuous play) - [ ] Multiplayer stress test passed (if applicable) - [ ] All critical user paths tested on every platform - [ ] Edge cases tested (full storage, no network, suspend/resume) ### Platform Certification - [ ] PC: Steam/Epic/GOG SDK requirements met - [ ] Console: TRC/TCR/Lotcheck submission prepared - [ ] Mobile: App Store/Play Store guidelines compliant - [ ] Accessibility: minimum standards met (remapping, text scaling, colorblind) - [ ] Age ratings obtained (ESRB, PEGI, regional) ### Performance - [ ] Target FPS met on minimum spec hardware - [ ] Load times within budget on all platforms - [ ] Memory usage within budget on all platforms - [ ] Network bandwidth within targets (if multiplayer) - [ ] No frame hitches in critical gameplay moments --- ## 4. Store and Distribution ### Store Pages - [ ] Store page copy finalized and proofread - [ ] Screenshots current and per-platform resolution - [ ] Trailers current and approved - [ ] Key art and capsule images finalized - [ ] System requirements accurate (PC) - [ ] Pricing configured for all regions - [ ] Pre-purchase/wishlist campaigns active (if applicable) ### Legal - [ ] EULA finalized and approved by legal - [ ] Privacy policy published and linked - [ ] Third-party license attributions complete - [ ] Music/audio licensing verified - [ ] Trademark/IP clearance confirmed - [ ] GDPR/CCPA compliance verified (data collection, consent, deletion) --- ## 5. Infrastructure ### Servers (if multiplayer/online) - [ ] Production servers provisioned and load-tested - [ ] Auto-scaling configured and tested - [ ] Database backups configured - [ ] CDN configured for content delivery - [ ] DDoS protection active - [ ] Monitoring and alerting configured ### Analytics and Monitoring - [ ] Analytics pipeline verified and receiving data - [ ] Crash reporting active and dashboard accessible - [ ] Server monitoring dashboards live - [ ] Key metrics tracked: DAU, session length, retention, crashes - [ ] Alerts configured for critical thresholds --- ## 6. Community and Marketing ### Community Readiness - [ ] Community guidelines published - [ ] Moderation team briefed and tools ready - [ ] Discord/forum/social channels set up - [ ] FAQ and known issues page prepared - [ ] Support email/ticketing system active ### Marketing - [ ] Launch trailer published - [ ] Press/influencer review keys distributed - [ ] Social media launch posts scheduled - [ ] Launch day blog post/dev update drafted - [ ] Patch notes for launch version published ---
The Accessibility Specialist ensures the game is playable by the widest possible audience. They enforce accessibility standards, review UI for compliance, and design assistive features including remapping, text scaling, colorblind modes, and screen reader support.
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
The Analytics Engineer designs telemetry systems, player behavior tracking, A/B test frameworks, and data analysis pipelines. Use this agent for event tracking design, dashboard specification, A/B test design, or player behavior analysis methodology.
The Art Director owns the visual identity of the game: style guides, art bible, asset standards, color palettes, UI/UX visual design, and the art production pipeline. Use this agent for visual consistency reviews, asset spec creation, art bible maintenance, or UI visual direction.
The Audio Director owns the sonic identity of the game: music direction, sound design philosophy, audio implementation strategy, and mix balance. Use this agent for audio direction decisions, sound palette definition, music cue planning, or audio system architecture.
The community manager owns player-facing communication: patch notes, social media posts, community updates, player feedback collection, bug report triage from players, and crisis communication. They translate between development team and player community.
The Creative Director is the highest-level creative authority for the project. This agent makes binding decisions on game vision, tone, aesthetic direction, and resolves conflicts between design, art, narrative, and audio pillars. Use this agent when a decision affects the fundamental identity of the game or when department leads cannot reach consensus.
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.