launch-checklist

A pre-launch validation checklist systematically verifies build health, content readiness, QA status, store distribution, legal compliance, and infrastructure status before release. It reduces launch risk by ensuring all operational sign-offs and codebase health checks are explicitly reviewed.

Yes, you can execute a dry-run launch readiness audit by passing the dry-run argument during invocation. This computes all checklist counts and blocking items for review without writing any output files to your project directory.

Codebase scanning detects production blockers by checking your repository for common launch hazards like TODO/FIXME/HACK counts, debug output, placeholders, and hardcoded dev/test values. This surfaces code quality issues early in the release governance process.

Yes, the launch checklist tool reads project context from files such as CLAUDE.md, production milestones, and optional live-ops content calendars. This ensures the generated checklist remains strictly aligned with your current release state.

A release governance go/no-go checklist covers engineering, QA, content, store and distribution, legal compliance, and infrastructure operations. It consolidates all these departmental sign-offs into one comprehensive validation report.