Prompt library
Plan a product launch week by week
Working backward from a fixed date converts wishes into deadlines, and the single-claim consistency check catches the most common launch failure: five channels telling five stories. The day-after metrics with thresholds make the retro objective before the launch happens.
Last reviewed July 17, 2026
The prompt
Plan the launch of {{product}} on {{date}}.
Working backward from launch day, produce a week-by-week plan covering:
1. Asset list: every artifact needed (page, demo, email, posts, docs), each with owner role and the week it must be final.
2. Channel plan: for each channel we control ({{channels}}), what goes out on launch day and what in the two weeks after; one line of intended message per channel.
3. The story: the one-sentence claim every asset must agree on. Flag any asset in your own plan whose natural message would drift from it.
4. Risk table: the 4 most likely launch failures (asset slips, low pickup, breaking bug, message confusion) with a trigger and a response for each.
5. Day-after list: the 5 metrics to check 24 hours in, with the number that would count as working.
Keep it executable by a small team; cut anything requiring people we did not mention.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{product}} | What is launching | the v2 of our reporting module |
| {{date}} | Launch date | September 10 |
| {{channels}} | Channels you actually control | blog, newsletter (8k), X account, changelog |