launch-checklist

To generate a game launch readiness checklist, the skill reads project files like milestones and release notes, then aggregates code health, content completeness, legal compliance, and infrastructure readiness into a single validation document.

Dry-run mode allows development teams to preview a full launch readiness checklist and validate cross-department tasks without creating actual sign-off entries or writing final files to the releases folder.

Yes, launch checklist automation systematically verifies legal compliance and marketing asset readiness alongside code health and content completeness, preventing missed cross-department tasks before the scheduled release.

Yes, context-aware analysis reads existing project files such as milestones, release notes, and content calendars to automatically populate relevant sections of the cross-department validation checklist.

Generating a comprehensive launch readiness checklist systematically validates infrastructure readiness alongside code quality and QA status, aggregating all pre-release requirements into one document for cross-department sign-off.

Yes, automated file output optionally writes the final launch readiness checklist directly to the releases folder, enabling version control and persistent tracking of cross-department validation status.