/team-launch — Launch Coordination Pipeline

Multi-department coordination for project go-live. All relevant departments, 6 phases.

Instructions

Phase 1: Pre-launch Audit (PARALLEL: qa-lead + seo-lead + security-auditor)

Spawn in parallel:

qa-lead:

• Final functional QA pass
• Regression testing on all critical paths
• Cross-browser and responsive verification
• Compile go/no-go status for QA

seo-lead:

• Sitemap.xml present and correct
• robots.txt configured properly
• All pages have unique title/meta
• Canonical tags set
• Structured data validated
• Redirect map (old URLs → new URLs if migration)
• Compile go/no-go status for SEO

security-auditor:

• Security headers configured (CSP, HSTS, X-Frame-Options)
• SSL certificate valid and not expiring soon
• OWASP quick scan — no critical vulnerabilities
• Dependencies audited (no known CVEs)
• Compile go/no-go status for Security

Present consolidated go/no-go status: | Area | Status | Blockers | | QA | GO/NO-GO | [details] | | SEO | GO/NO-GO | [details] | | Security | GO/NO-GO | [details] |

USER APPROVAL GATE — Go/No-go decision.

Phase 2: Content Freeze (content-lead)

Spawn content-lead to:

• Final content review — all copy proofread
• All images optimized and alt-tagged
• Legal/compliance check (privacy policy, terms, cookie consent)
• Content signoff confirmation

Phase 3: Technical Preparation (devops-engineer)

Spawn devops-engineer to:

• Production environment verification
• Database migrations ready and tested
• CDN and caching configured
• Backup procedures verified
• Monitoring and alerting active (Sentry, UptimeRobot)
• Rollback plan documented:
  1. What triggers rollback
  2. Rollback steps
  3. Communication plan during rollback
  4. Recovery timeline

Phase 4: Launch Execution (project-lead)

Spawn project-lead to create launch runbook:

Pre-launch (T-1 hour):

• Final backup of existing site (if migration)
• Team notified and standing by
• Monitoring dashboards open

Launch (T-0):

• DNS switch / deployment trigger
• Wait for propagation (5-15 min)
• Verify site loads on production URL
• Run smoke test checklist:
  • Homepage loads
  • Navigation works
  • Key forms submit
  • Authentication works
  • SSL certificate valid
  • No console errors
• Verify redirects (old URLs → new URLs)
• Verify analytics tracking fires

Post-launch (T+30 min):

• Monitor error rates
• Check Core Web Vitals
• Verify email delivery (if applicable)

Phase 5: Post-launch (PARALLEL: analytics-specialist + marketing-lead)

Spawn in parallel:

analytics-specialist:

• Verify all tracking is firing correctly
• Confirm conversion events recording
• First data sanity check
• Set up automated alerts for anomalies

marketing-lead:

• Launch announcement — social media posts
• Email announcement to subscriber list
• PR/outreach if planned
• Community notifications

Monitor for 30 minutes for issues.

Phase 6: Handover (account-director)

Spawn account-director to:

• Trigger /handover workflow for documentation
• Create client training session outline
• Define support transition plan (warranty period, SLA)
• Schedule project retrospective
• Final project sign-off

Update production/session-state/active.md:

## Current Phase: Completed
## Launch Date: [date]

Present project completion summary.