release-checklist

To create a pre-release validation checklist, run the release-checklist command with your target platform to scan project context, milestone files, and codebase issue markers, generating a structured launch readiness document for build verification and QA signoff.

Launch readiness validation is the process of verifying build stability, QA signoff, and store metadata before a release. It matters because it prevents last-minute launch failures by consolidating scattered quality gates and code health checks into a single comprehensive checklist.

Yes, release checklist generation supports PC, console, and mobile scenarios. You specify the target platform when invoking the command, such as /release-checklist pc, and it drafts a platform-specific checklist covering build verification and distribution readiness.

Codebase issue markers like TODO, FIXME, and HACK are scanned and counted to assess launch readiness. Locating these items helps surface likely blockers and review needs, directly informing the no-go decision support and QA signoff preparation process.

The best way to align a release checklist with actual shipping content is to read project context from CLAUDE.md and milestone status from production directories. This project-context driven validation ensures the checklist matches the current milestones and release scope.

You should not rely solely on an automated release checklist when you lack explicit project context files like CLAUDE.md or milestone tracking data. The validation requires these inputs to draft a structured checklist and accurately support the launch no-go decision.