launch-checklist

A launch readiness checklist evaluates project context and codebase health to produce department coverage for code, content, QA, store compliance, infrastructure, and operations. It summarizes blocking versus conditional items and specifies required sign-offs for a formal READY, NOT READY, or CONDITIONAL outcome.

Yes, a dry-run mode generates the comprehensive launch readiness checklist without writing any sign-off artifacts. This allows you to validate project context and scan for placeholder or risk patterns safely before committing to a specific date-targeted release run.

You need to provide relevant project files such as CLAUDE.md, production milestones, releases, and an optional live-ops content calendar. The checklist process reads these files to evaluate project context and scan for known debugging patterns.

It scans the codebase for health issues, debugging patterns, placeholders, and risk patterns to categorize launch items. It then produces a decision-ready output separating blocking items that halt release from conditional items that require specific sign-offs.

A comprehensive launch readiness checklist includes dedicated store and legal coverage by evaluating project milestones and distribution readiness. It aggregates these checks into a formal go/no-go sign-off list to ensure all compliance requirements are met before release.