Free ChatGPT Project · runs on GPT-6 Astra
A GPT-6 Astra prompt that writes each post from what that person actually saw, checks that no 2 posts share a sentence, and tells you which 3 to publish first.
Free. Includes the instructions, the roster template and a worked example. Set it up once as a ChatGPT Project and it's there wherever you open ChatGPT, the phone app included.
12 people resharing the announcement reads as marketing copy 12 times. 12 people each saying what they saw reads as 12 things that happened. Same launch, same day, no shared sentences, and each person approves their own.
See how Supergrow does this for 40 peopleMy name is Deven and I'm the founder of supergrow.ai. Supergrow is the LinkedIn content platform for B2B teams. We interview each person for 10 to 15 minutes, model how they actually write, and turn what they said into posts in their own voice. Marketing drafts, the person approves, and it publishes.
We don't generate posts from a topic. We extract them from the person. This prompt is the smallest version of that idea I could fit in 1 file: give GPT-6 Astra 1 line on what each person saw, and it writes from the line instead of from the announcement.
Bootstrapped since 2023 · profitable, no investors · #1 Product of the Day and Week, Product Hunt, 19 February 2024
Why this happens
Marketing writes the announcement. It goes in Slack with "feel free to share". 12 people reshare it, 3 add "so proud of the team", and the feed sees the same sentence 12 times from 12 faces. Nobody reads past the first one.
All 12 of those people saw something different. The engineer deleted a version. The seller lost a deal over it. Support took the complaints for 6 months. That's 12 posts, and none of them start with "excited to announce". The prompt writes those, from 1 line per person, and refuses to write when the line is only a job title.
Who this is for
For
Not for
Time it takes
Before you start
4 things. The second one is where most of the effort goes, and it's also the whole reason the posts come out different.
Before you paste anything. The roster can hold unreleased launches, customer details, lost deals and internal mistakes. Use an approved work account, remove customer identifiers, and don't upload confidential launch material unless your company policy allows it.
A title is not a line. "Led the launch" gives the prompt nothing to write from, so it asks you a question instead of inventing a story. That's on purpose.
Led the launch.A role. Nothing happened in it.
Was part of the team that built it.True of everyone on the roster.
Supported the rollout from the finance side.Still a title, with more words.
We threw the first version away in week 6 because the main query took 40 seconds.A thing that went wrong, with a number.
Lost a deal in March because the buyer asked for this and we said next year.A moment they were in.
I pushed to ship in Q1. The team said no. They were right.A change of mind.
Quick start
Open ChatGPT, pick GPT-6 Astra in the model menu, create a Project called Team Post and paste TEAM-POST.md into its instructions. No Projects on your plan, paste it at the top of a chat instead.
ROSTER.mdThe announcement, the marketing copy if you have it, and 1 line per person. Or build it below and copy it out.
You get 1 post per person, the line each came from, a question for anyone whose line was thin, and the 3 to publish first.
Send each post to its own person. Nobody publishes a post they haven't read.
Build your roster · try it here
Type the announcement and 1 line per person. The check under each line tells you whether the prompt would write from it or ask you a question. Then copy the whole roster out. Nothing is saved or sent anywhere.
Paste what you copied into the Project and say "run team post". The check here is a rough version of the prompt's own thin-line rule, so a line that passes here can still come back as a question.
Worked example
The company, the people and the numbers are invented so you can see the shape of the output. The announcement was a reporting dashboard that replaced a weekly CSV export. Ana's line was "supported the launch", so she got a question instead of a post. Every detail in the 4 posts is in the line under it or in the announcement, which is the rule the prompt holds itself to.
The CEO doesn't go first. His post reads as the announcement again until the other 3 have turned it into a story.
Overlap check · try it here
Paste 2 or more posts, separated by a line with 3 dashes, and the marketing copy if you have it. It finds any run of 6 or more words that shows up in 2 posts, or in a post and the copy. Runs in your browser, nothing leaves the page.
The prompt
Open a file to read it or copy it. The instructions are 1 file. The roster is the input. The example is there so you know what good output looks like before you send anything to a colleague.
Get it
The folder includes:
TEAM-POST.mdthe instructions, pasted into the Project onceROSTER.mdthe input template you fill in per launchexample.mda made-up launch run through the promptREADME.mdsetup in 5 minutes, with and without ProjectsSet it up in 5 minutes. Fill in the roster for your next launch. Send each post to its person.
Or copy any file from the 4 files above.
Where Supergrow comes in
You know what each of them saw. You type 4 lines.
You're chasing 12 people on Slack for 1 sentence each, the day before the launch.
You don't know what most of them saw, and neither does the prompt.
PostCast interviews each person for 10 to 15 minutes and asks the follow-ups, so nobody has to type up what they saw in a Slack thread the night before. Content DNA holds how each person writes. The draft goes to that person for a 1-tap yes, and it publishes without anyone sharing a LinkedIn password.
When it breaks
The lines were titles. Go back to those people and ask for 1 moment with a date on it. The prompt is right to wait.
2 people gave you the same moment. Keep both, but each needs a detail the other doesn't have. Ask 1 of them for it.
The line underneath it was thin and the prompt leaned on the announcement to fill the space. Treat it as a question, not a post.
Their post is the one that most resembles the announcement. Day 3, after the others, it reads as the story's ending instead of its press release.
They're allowed to. It's their post. Run the overlap check on the final versions so you at least know it happened.
The prompt scales. Collecting 30 lines the day before doesn't. That's the point where the interview has to come from the tool.
Supergrow does the part this prompt can't: it gets what each person saw out of their head, in their words, without you chasing anyone on Slack.
Deven Bhooshan, founder of Supergrow