Create a product launch checklist with go-to-market sequencing

Description

You're two weeks from a major feature launch and realize there's no coordinated plan across product, marketing, sales, and support. This creates a sequenced launch checklist that ensures nothing falls through the cracks — from beta testing through post-launch monitoring.

Create a comprehensive product launch checklist for {{feature_name}} in {{product_name}} with proper go-to-market sequencing.

## Context
- Product: {{product_name}}
- Feature being launched: {{feature_name}}
- Launch date: {{launch_date}}
- Launch type: {{launch_type}} (silent / soft / major announcement)
- Target audience: {{target_audience}}
- Key stakeholders: {{stakeholders}}
- Dependencies or risks: {{known_risks}}

## Phase 1: Pre-Launch (T-14 to T-7 days)
### Product & Engineering
1. Feature freeze date and criteria for "launch-ready"
2. Beta testing results: key metrics and unresolved bugs
3. Feature flag or staged rollout plan (% of users per day)
4. Performance benchmarks and load testing results
5. Rollback plan: what triggers a rollback and who makes the call?

### Documentation & Enablement
1. Internal knowledge base articles for support team
2. Sales enablement materials (deck, FAQ, objection handlers)
3. Customer-facing help docs and in-app guidance
4. API documentation updates (if applicable)

## Phase 2: Launch Week (T-7 to T-0)
### Marketing & Communications
1. Blog post / announcement draft — reviewed and approved
2. Email announcement segmented by user type
3. Social media content calendar for launch day ± 3 days
4. Press or analyst briefings (for major launches)
5. In-app announcement or notification plan

### Sales & Customer Success
1. Priority customer list for personal outreach
2. Sales script updates with new feature talking points
3. CS team briefed on common questions and edge cases
4. Upgrade path defined for customers who need the new feature

## Phase 3: Launch Day (T-0)
1. Deploy sequence with specific times and responsible owners
2. Monitoring dashboard: error rates, latency, feature adoption
3. War room / Slack channel for real-time issue triage
4. Go/no-go check at T-1 hour: all systems green?
5. Customer communication sends (email, in-app, social)

## Phase 4: Post-Launch (T+1 to T+14)
1. Day 1 metrics review: adoption rate, error rate, support tickets
2. Day 3 check: early user feedback synthesis
3. Day 7 retrospective: what worked, what didn't, what to improve
4. Day 14 impact report: feature adoption vs. targets, customer feedback themes
5. Decision: iterate, expand rollout, or pull back?

## RACI Matrix
Create a table assigning Responsible, Accountable, Consulted, Informed for each checklist item:
| Task | Product | Engineering | Marketing | Sales | Support |
|------|---------|-------------|-----------|-------|---------|

Customize This Prompt