launch-readiness

1

mohitagw15856/pm-claude-skillsProduct ManagementAudit pendingSnapshot c79463ed2822

Escalation path defined for launch issues

Customer success briefed (if enterprise)

Process

Review provided launch brief and checklist responses
Flag any incomplete items as blockers (must fix) or risks (monitor)
Assess overall readiness and produce go/no-go recommendation with rationale
If no-go, specify exactly what must be completed and by when
Validate — Confirm every blocker has a named owner and resolution deadline, and that the rollback plan is tested (not just documented)

Launch Date: [date] Launch Tier: [1 / 2 / 3] Overall Status: ✅ Go / ⚠️ Conditional Go / 🛑 No-Go

Blockers (must resolve before launch):

Risks (monitor closely):

Ready Areas:

Recommendation: [Clear go/no-go with rationale — 3-5 sentences]

Do not mark a function as "Ready" without evidence — green status must be backed by a completed checklist item, not an assumption
Do not issue a Conditional Go without specifying exactly what conditions must be met and by when — vague conditions are not conditions
Do not treat the rollback plan as complete unless it has been tested in staging, not just documented
Do not assign blockers to "the team" — every blocker must have a single named owner or it will not be resolved before launch
Do not skip the analytics verification step — unverified tracking events mean the launch will be invisible and cannot be evaluated