Launch post
From what actually shipped, in your voice.
- 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
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
Starts from what shipped
Pull requests, snapshots and decisions, not the roadmap. Anything still rolling out is left out or labelled.Writes in your voice
Using the brief your team keeps in onecell, so the post sounds like the last one.Lists every claim with a source
One table a reviewer can scan in thirty seconds.Checks itself before showing you
The voice rules run on the draft first. Nothing is posted.
What you get back
Open the full example →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.
Example launch post: decisions you can find again
Headlines
- Decisions, kept where the next agent looks. (pick)
- Write the decision down once. Every agent finds it.
- The call, the reason, and who made it.
Post
A team makes decisions all day. Most of them end up in a chat that closes, a pull request that merges, or someone's head.
onecell now has a decision block. It holds the question, the context, the call and what it commits you to. When someone accepts it, onecell records who and when. Nobody can type another person's name into it.
Your agent can write one from the conversation you are having, or from the pull request that carries it. Ask it what is still open, and it lists every proposed decision in your cells, each with a link.
The point is the next session. A new agent, or a new teammate, asks where something was decided and gets the answer with a citation: cell, heading, passage. Not a vibe.
Thread
- Decisions made in chat end when the chat does. onecell now keeps them as a block: the question, the call, the reason.
- Accept one and onecell records who and when. The name is stamped by the server, so an agent cannot put words in your mouth.
- Ask your agent what is still open. It lists every proposed decision, each with a link. The next session starts there.
Claims checked
| Claim | Source | Live for everyone? |
|---|---|---|
| A decision block holds the question, context, decision and consequences | #65 | Yes |
| onecell records who accepted it and when; a client cannot set the name | #66 | Yes |
| Your agent can list open decisions with links | #66 (list_decisions) | Yes |
| Answers cite cell, heading and passage | Search, shipped before this release | Yes |
| Lists decisions across every cluster | #67 | Left out: the brief says to claim several clusters carefully |
Variations
A changelog entry
Ask for one plain paragraph per change, newest first, with no headline options. Pair it with the Repo snapshot recipe to cover a week.
An email to customers
Add: “Write it as an email to <audience>: a subject line, four short paragraphs, one link.” Send it yourself after reading it.
Several channels at once
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.
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.