launch-checklist

A launch readiness checklist validates go-live readiness by assembling a comprehensive go/no-go report. It assesses code health, data readiness, infrastructure, and operational sign-offs to prevent incomplete areas from blocking your target release date.

To create a go/no-go checklist, scan the repository for launch blockers like TODOs, debug output, and exposed secrets. The skill generates a domain-aware report covering codebase health, deployment, rollback, and on-call readiness for final sign-offs.

Yes, the launch readiness review works for both product and game repositories. It detects the domain orientation of the codebase and adapts the generated checklist to assess the specific launch risks and operational requirements of that domain.

You need to provide repository context, milestone and release artifacts, and access for codebase health scans. This allows the assessment to evaluate blocking and conditional items, producing a decision-friendly report for dry runs or specified launch dates.

The launch risk assessment flags TODOs, debug output, hardcoded test values, and exposed secrets as launch blockers. Identifying these issues before deployment ensures the final operational sign-off covers critical deployment and rollback procedures.

Yes, the checklist organizes on-call, rollback, monitoring, and communication readiness into a decision-friendly report. This operational sign-off support helps release managers track incomplete areas and prepare final approvals for the launch date.