Launch post prompt (copy-paste product announcement)

Here is a copy-paste launch post prompt you can use right now. Paste it into a sfora post, or hand it to your AI agent, fill in a few bullets about what you shipped, and you get back a real product announcement — one that opens with what changed, says who it is for, and ends with a clear next step. The output is a markdown file on your board, not a chat message you copy out by hand.

This is one of the prompts in our AI prompts guide. If you are drafting the release doc that leads up to the launch, pair it with the PRD prompt, and for the deeper background on writing specs with AI, see the AI PRDs guide.

The prompt

Copy this block, paste it where you draft, and replace the bracketed parts.

You are helping me write a product launch post. Write it in plain, direct
language — short sentences, no marketing fluff, no words like "seamless,"
"powerful," or "revolutionary." Write like you are telling a colleague what
shipped.

Here is what I am announcing:

- **What shipped:** <the feature or release, in one line>
- **Who it is for:** <the people who will care>
- **The problem it solves:** <what was annoying or impossible before>
- **How it works:** <2–3 bullets on what someone actually does>
- **Availability:** <who can use it now — everyone, beta, a plan tier>

Write the post with this shape:

1. **Headline** — the one thing that changed, phrased the way a person would say it.
2. **Opening line** — what you can do now that you could not do yesterday. No
   backstory, no "we're excited."
3. **Why it matters** — one short paragraph on the problem this removes.
4. **How to use it** — a short list of concrete steps.
5. **What's next / caveats** — anything not done yet, stated honestly.
6. **Call to action** — the single next step to take.

Keep it under 300 words. Use sentence case in headings. Do not invent metrics or
quotes. If something is missing from my notes, leave a `<!-- TODO -->` note
instead of making it up.

Running it in sfora

You do not have to leave your workspace to use this. In sfora, a post is a markdown file, so the prompt and the output live in the same place as the work.

There are two ways to run it:

• Paste it into a post. Open a new post, paste the block, fill in your bullets, and hand it to the agent in that thread. It replies with the drafted post, right there.
• Hand it to your agent over the CLI. If you drive an agent like Claude Code, Cursor, or the sfora CLI over MCP, give it the same prompt and point it at the board. It writes the post as a file you can open and edit.

Either way, the result is a real markdown post on your board that a person can read, comment on, and edit — not a block of text trapped in a chat window.

What the output looks like

Feed the prompt a few bullets and you get back something like this — a post you can publish after a light edit:

# CSV export is now one click

You can now export any board to CSV from the board menu. No more copy-pasting
rows into a spreadsheet — pick "Export to CSV," and the file downloads.

## Why we did this

People kept pulling their tasks into spreadsheets to share status with folks
outside the workspace. That meant hand-copying rows every week and re-copying
when anything changed. Now the export is a click, and it always matches what is
on the board.

## How to use it

1. Open the board you want.
2. Click the board menu (top right).
3. Choose "Export to CSV." The file downloads with the visible columns.

## Notes

- The export includes only the rows you can currently see, so filters apply.
- Scheduled and recurring exports aren't here yet — that's next.

Available to everyone today. Give it a try on your busiest board.

Notice what it did and did not do: it opened with the change, kept the "why" to one paragraph, listed real steps, and stated a caveat honestly instead of pretending the feature is finished. That is the whole point of the prompt — it holds the shape so you can focus on the facts.

How to get a better draft

The prompt is only as good as the bullets you feed it. A few things sharpen the output:

• Be specific about the problem. "Copy-pasting rows into a spreadsheet every Monday" gives the AI something real to write about. "Improve exports" does not.
• Say who it is for. A post for admins reads differently than one for every member. Name the audience and the draft matches it.
• List the actual steps. If you tell the AI the three clicks, it writes accurate instructions. If you leave it vague, it will guess — and you will spend your edit fixing invented steps.
• Call out what is not done. Honest caveats build trust and save you support tickets. The prompt asks for them on purpose.

Where sfora fits

sfora is a project workspace where humans and AI agents are members of the same team, and where everything — tasks, docs, posts — is a markdown file. That is what makes this prompt more than a chat trick.

When you run the launch post prompt in sfora, the announcement is a real file on your board. A person edits it and publishes it; an agent that is a member of the same workspace can draft it, link it to the tasks that shipped, and keep it next to the work it describes. The post is not a copy you pasted out of a chatbot — it is a document in the same place your team already works.

Want the doc that comes before the launch? Use the PRD prompt to draft the spec, and browse the full set in the AI prompts guide.