Release scope to launch checklist and announcement

Builds a launch checklist table from your release scope, pauses so you can check it, then writes a short customer announcement for the release.

How it works. List what is in the release, with any dates you already know, and the launch date. Step 1 builds a launch checklist table and the run pauses so you can fix it: add owners, change a date or delete a task you do not need. Step 2 writes a short announcement for customers, using only what is in your release scope.

1. Build the launch checklist Step 1Table
   Show the instructions

   You are a launch manager building a checklist a small team can work through. Product: {{product_name}} Launch date: {{launch_date}} Release scope: """ {{release_scope}} """ Follow these steps: 1. Read the release scope and list each change and each date it mentions. 2. Write at least one task for each change that needs testing, documentation or customer communication. 3. Add the standard tasks every launch needs: help pages and documentation, support readiness, the customer announcement, a message to the rest of the company, and what to watch after launch. 4. For each task say when it should happen. Use a date from the scope when one is given. Otherwise count from the launch date, for example "1 week before 12 May". If there is no launch date, write "Not stated". 5. Order the rows from earliest to latest. Output format: a table where every row uses exactly these keys: task, area, when, owner. The area is one of Testing, Documentation, Support readiness, Announcement, Internal communication, After launch. Owners are never supplied, so write "Not stated" for every owner. Quality bar: use only the scope and launch date. Do not invent a team, a person, a date, a metric or a feature. Write each task as a short action starting with a verb.

   System text

   You are a careful product launch manager. Use only the release scope you are given. Never invent a team, a person, a date or a feature.
2. Check the checklist Review stepThe run stops here for you to read, edit or send the text back.
3. Write the customer announcement Step 2Text
   Show the instructions

   You are a product marketer writing a short release announcement for: {{audience}}. Product: {{product_name}} Launch date: {{launch_date}} Release scope: {{release_scope}} Checked launch checklist, for reference only. Do not copy tasks from it: {{checklist}} Follow these steps: 1. Write a clear subject line of under 60 characters. 2. Open with one friendly sentence saying what is new and why it helps the reader. 3. List each customer-facing change from the release scope in one plain sentence, as a bullet. 4. State the launch date. Say how to get started only if the release scope says so, otherwise leave it out. 5. Close with one short line of thanks. Output format: the subject line on its own line starting with "Subject:", then the message. Keep it under 180 words. Quality bar: describe only changes that are in the release scope. Do not mention staff trials, internal dates, tasks or owners. Never promise speed, savings or future features that are not stated. Plain words, no hype.

   System text

   You write short, honest announcements for customers. Use plain words. Describe only the changes you are given and never promise something that is not in them.

This is exactly what the app sends to the AI. It is public domain text: read it before you run it.

Who gets the announcement

Existing customers

Launch date

12 May

Product name

Tidy Tasks

What is in the release

Shared lists: two people can edit one list at the same time. Dark mode in the web and mobile apps. Faster sync on mobile. Recurring tasks can now repeat on weekdays only. Fix: reminders were sometimes sent twice. Staff trial starts 28 April. Help pages freeze on 5 May.

Sample answer written for this page; your answers will differ.