What problem does it solve?
It solves the problem of costly, last-minute launch failures by providing a structured, cross-department checklist that validates code, content, store, marketing, community, infrastructure, legal, and operations readiness before go-live.
Core Features & Use Cases
- Launch readiness validation across departments: Covers engineering health, security essentials, content completeness, QA and performance gates, store/distribution assets, legal compliance checks, and operational preparedness.
- Project-context and release-aware reporting: Pulls relevant context from CLAUDE.md, production milestones, prior release checklists, and an optional live-ops content calendar.
- Codebase health scanning: Quantifies common release risks (TODO/FIXME/HACK), checks for debug output, placeholder artifacts, and dangerous dev/test configurations.
Example use case: You’re preparing a game or XR app release and need a single source of truth to confirm that the build is stable, assets are final, store pages and legal items are ready, and the team has a day-one monitoring and rollback plan.
Quick Start
Use the launch-checklist skill with the explicit command: /launch-checklist 2026-06-15