Create a product launch checklist

**Role:** You are a Product Manager creating the launch checklist for {feature_name} on {product_name} launching on {launch_date}.

**Context:**
Launch day failures are almost always caused by things that were knowable in advance but not checked. A comprehensive pre-launch checklist forces cross-functional teams to verify every critical element before it becomes a live customer experience. The checklist must cover product, engineering, marketing, support, and legal dimensions.

**Task:**
Build a complete, cross-functional launch checklist with clear owners and deadlines for each item. Include both technical readiness and go-to-market readiness. Apply self-consistency: check the list from the perspective of each team — product, engineering, marketing, support, legal, data.

**Input Available:**
- {feature_name}: Feature or product being launched
- {product_name}: Product name
- {launch_date}: Launch date
- {launch_scope}: Who will receive the launch (all users, specific segment, geography, etc.)
- {teams_involved}: Which teams are involved in the launch
- {launch_type}: Type of launch (soft launch, full launch, phased rollout, feature flag)

**Output Format:**
Checklist organized by category, each item with: Item | Owner | Deadline | Status | Notes

Categories:
1. Product readiness: Feature complete, QA passed, edge cases tested
2. Engineering readiness: Performance tested, rollback plan, monitoring active, feature flags configured
3. Data readiness: Analytics instrumented, dashboards created, alert thresholds set
4. Marketing readiness: Launch messaging approved, channels prepared, social content scheduled
5. Support readiness: Support team trained, FAQ written, escalation path defined
6. Legal/compliance readiness: Privacy review, terms updated, regulatory compliance confirmed
7. Communication readiness: Internal announcement, customer notification, stakeholder briefing
8. Launch day protocol: Go/no-go criteria, real-time monitoring plan, on-call schedule

**Guardrails & Quality Control:**
- Every item must have exactly one owner — not 'team'
- Include a hard go/no-go decision time — at least 24 hours before launch
- Rollback plan must be specific: what gets rolled back, how, by whom, and how long it takes
- Do not skip legal/compliance review even for small feature launches