launch-checklist

Game launch readiness validation reviews codebase health, content readiness, store compliance, and infrastructure stability to prevent broken releases. It generates a department-by-department checklist catching debug markers, placeholder assets, incomplete localization, and unfinalized store materials.

Generate a comprehensive pre-launch checklist by reading project context files like CLAUDE.md and milestone documentation, then validating build health, testing, performance, assets, localization, store materials, legal compliance, infrastructure, and analytics. Invoke the skill in dry-run mode to produce a complete readiness plan without writing files.

Yes, launch readiness scanning reviews project context and checks codebase health by locating debug markers like TODO, FIXME, and HACK hotspots. It also identifies missing or placeholder assets, incomplete localization, and operational gaps across multiple departments.

Yes, the launch checklist covers store compliance and legal preparation by validating finalized store materials, legal items, and release artifacts. It produces a structured readiness output spanning build, content, store, infrastructure, analytics, and community operations.

Run a dry-run launch readiness check by invoking the skill in dry-run mode to generate a complete readiness plan without writing sign-off artifacts or output files. This allows safer planning by reviewing the department-by-department checklist before committing to a dated release checklist file.

An end-to-end pre-launch readiness scan requires project context files like CLAUDE.md and milestone or release checklist documentation. These files provide the necessary context to validate build health, content readiness, infrastructure, analytics, and final go/no-go sign-offs across departments.