One post or a thread
When a thought fits one screen, and when it genuinely needs unpacking.
The prompt
You are an editor. Decide whether a text is one post or a thread. The text: {paste} Subject: {what it is} What the reader should take away: {one thought} Work through: 1. How many thoughts are in it. One thought is one post, always. A thread caused by length rather than by count reads as padded. 2. If there are several: are they sequential. A thread works when point two makes no sense without point one. If the points are independent, that is a list in one post. 3. How to compress to one screen: what to cut. Usually the preamble, the repetitions, and explaining what was already clear. 4. If a thread is warranted: how to build the first post. It must work alone — most people read only that. 5. How to end each node so people continue. 6. The maximum number of nodes. After the fifth almost nobody follows, and a second thread the next day works better. 7. What a thread costs: discussion smears across the nodes and the comments stay empty. The default is one post. A thread has to be justified, not chosen by habit.
Anything in curly braces is yours to replace.
Example output
One thought: "short prompts work better." So, one post. Cut: two paragraphs on how you got there. They do not fit, and the comments are where you tell it. Were it a thread: node one is the conclusion, not the preamble. Everyone reads that, half read the rest. Maximum: 4 nodes.
Related prompts
The first line decides everything: on a phone only about 90 characters show before «more». Hooks are written to that limit.
Write 20 opening lines for Threads posts on the topic "{topic}". Audience: {who} My role: {who you are to them — practitioner, seller, observer} Hard limits: — No line longer than 90 characters. That is what shows in the feed before someone taps "more"; anything past it goes unread if the first part didn't land. — No "Did you know that", "Top 5 ways", "Here's a roundup" — these read as templates and get scrolled past. — No caps lock, no emoji chains. Give 4 groups of 5: 1. Personal experience with a specific number or timeframe. 2. Disagreement with received wisdom in the niche. 3. An observation the reader recognises in themselves. 4. An open question they have something to answer from their own experience. After each line, in brackets, say what reply it is built for. If the only possible reply is "agreed" — rewrite it: that hook collects likes, not conversation.
Show sample resultHide sample
Personal experience: "Posted on Threads daily for six months. First four months: about 30 views each." (expecting: "so what changed in month five?") Disagreement: "Posting at the best time is advice that will do nothing for you. Here's why." (expecting: pushback from people who believe in timing)
Replies are the strongest signal in the recommendation feed. This post is assembled so people want to write, not silently like.
Write a Threads post on the topic "{topic}" designed to pull replies. What I know about it: {your experience, facts, numbers} Audience: {who} What I want to hear in the replies: {e.g. how other people solve this} Rules: — No longer than 500 characters, that is the platform limit. 300 is better. — The first 90 characters must work as a standalone hook; the rest is what people unfold themselves. — End on a question the reader already has an answer to from their own experience. Not "what do you think?" but something specific: their case, their number, their choice. — Leave a place in the text where the reader can disagree. A post everyone agrees with gives nobody anything to say. Don't do this: — "Tell me in the comments!" — a direct ask works worse than a question people simply have something to say to. — Don't invent provocation for the sake of an argument. A fight collects replies once, and then people unfollow. Give 3 versions of the post and, under each, what kind of reply it is most likely to collect.
Show sample resultHide sample
Version 1 (298 characters): "I let go of the strongest person on the team. He was right more often than anyone — and that was the problem. He didn't argue, he explained. After a few of those explanations people stopped offering their own ideas — why bother if you'll turn out wrong anyway. One strong voice can quietly switch off everyone else. Has this happened to you, and how did you handle it?" Will collect: stories about people's own "too-right" colleagues, and an argument about whether letting them go was right.
The feed watches speed: 20 replies in half an hour push a post further than 50 over a day. A plan for that window.
This prompt is part of the PRO collection
Unlock accessA link in the body sends people off-platform, and the feed accounts for that. The scheme: the post stands alone, the link comes as the first reply.
This prompt is part of the PRO collection
Unlock access