Prompt Details
Model
(claude-5-sonnet)
Token size
605
Example input
[describe the launch, the date, and everything you believe is in scope]: a SaaS billing tier release going live on the 14th, in scope: new pricing page, billing migration, support macros
[paste your plan, checklist, or status notes]: the internal launch checklist and status notes for the release
[type of launch, team size, hard deadline]: software release, team of nine, hard deadline the 14th
[paste your list of gaps, tasks, or concerns]: the open items list from the release checklist
[describe the launch and the single riskiest part of it]: the billing migration, riskiest part is the production data migration
Example output
External dependency with no owner: the pricing page copy is listed as done, but the change has to go live through the marketing CMS, which nobody on the engineering checklist has access to. This is a hard blocker on launch morning, not a task.
Breaks only after launch: there is no entry in the support macro list for the new billing tier. Day-one upgrade questions will land on an inbox with no scripted answer, during the exact window where the team is watching dashboards instead of tickets.
Marked done, not verified: migrations tested has no named person and no staging run referenced. A migration that has been written is not a migration that has been run against production-shaped data.
Instant access
Commercial use
Money‑backBy purchasing this prompt, you agree to our terms of service
CLAUDE-5-SONNET
Most launches don't fail on the big stuff - they fail on the one thing nobody owned. This Claude prompt pack audits any launch before it goes live: it maps what you're actually shipping, hunts the gaps you stopped seeing weeks ago, separates real blockers from nice-to-haves, and writes the rollback plan you'll wish you had at 2am. Works for software releases, marketing campaigns, events, and migrations. Includes a reusable Claude Project template. Free tier of Claude.ai works fine.
...more
Added 2 weeks ago
