Prepare Features for Safe Launch

Generates launch checklists that scale to your feature's risk so you catch issues before they reach users and know what to monitor post-launch. It moves past generic launch tasks to specific verifiable actions (e.g. 'verify signup flow end-to-end in staging with Gmail, Outlook, and corporate SSO'). It ties monitoring thresholds to rollback criteria so you ship with confidence.

1. Say 'launch checklist' or 'am I ready to launch?'. 2. Claude asks what you're launching, your launch date, user scope, and risk level (high/medium/low). 3. It generates a risk-scaled checklist with: pre-launch phase (QA, rollback plan, metrics setup, support briefing), launch-day phase (deploy window, verification, comms), and post-launch phases (48 hours and 1 week). Each item has an owner and a deadline. Monitoring thresholds are specific (e.g., 'error rate above 0.5% triggers code yellow'). Output: a checklist your team can execute without ambiguity, with clear go/no-go criteria at each stage.

Triggered by 'launch checklist', 'pre-launch check', 'ready to launch?', or 'launch prep'. Requires feature scope, launch date, user count, and risk assessment. Includes recommendation against Friday afternoon launches.