# Recipe: launch post, from what actually shipped, in your voice

A copy-paste prompt: your agent writes headlines, a short post and a thread for a release, checks every claim against what shipped, and runs your voice rules.

> [!info]
> **For:** a content marketer, or a founder announcing their own work. **When:** when something ships. **Takes:** a few minutes of agent time. **You get:** three headlines, a short post, a three-part thread and a table of every claim with its source and whether it is live for everyone.

## The prompt

```text
Write a launch post for <feature or release> in our voice, from what
actually shipped. Save it to <cell>.

1. Gather the facts: the repo snapshot or pull requests for it, the
   decisions behind it (list_decisions), and our voice and claim rules
   (search for the brand brief). Check who can use it today. If it is
   behind a flag or still rolling out, don't present it as available to
   everyone.

2. Draft "Launch: <feature>" with create_document (dry run first):
   - three headline options
   - a short post, under 200 words, that names the thing and shows it
   - a three-part social thread
   - a table of every claim, its source (pull request or document), and
     whether it is live for everyone

3. Check the draft against the voice rules and fix what fails before
   showing me.

4. Reply with the link and your pick of headline. Don't publish or
   post anything.
```

## What your agent does

1. Starts from what shipped
   Pull requests, snapshots and decisions, not the roadmap. Anything still rolling out is left out or labelled.
2. Writes in your voice
   Using the brief your team keeps in onecell, so the post sounds like the last one.
3. Lists every claim with a source
   One table a reviewer can scan in thirty seconds.
4. Checks itself before showing you
   The voice rules run on the draft first. Nothing is posted.

## What you get

A real post for onecell's decision blocks, from pull requests #65–#67. Note the claims table: listing decisions across every cluster shipped, but was left out on purpose.

<!-- onecell:block {"type":"embed","documentId":"9127af9d-0074-4596-b6b6-9348fe59e891"} -->
[Example launch post: decisions you can find again](https://onecell.io/p/example-launch-post-decision-blocks)

## Variations

<details>
<summary>A changelog entry</summary>

Ask for one plain paragraph per change, newest first, with no headline options. Pair it with the *Repo snapshot* recipe to cover a week.

</details>

<details>
<summary>An email to customers</summary>

Add: “Write it as an email to `<audience>`: a subject line, four short paragraphs, one link.” Send it yourself after reading it.

</details>

<details>
<summary>Several channels at once</summary>

Add the channels you use, such as a blog post, a LinkedIn post and a newsletter item. The claims table stays shared across all of them.

</details>

## Tips

- Name the thing in the first two sentences. People read the start and skip the rest.
- The claims table is the part to keep. Next quarter it shows what you said and why it was true.
- Run the *Brand voice check* recipe on anything a teammate wrote by hand.

---

Part of [onecell recipes](https://onecell.io/cells/recipes/6afc2a14-8a68-480d-99d8-7edd66893874): copy-paste prompts for using onecell in your work.