A list post that is not an article
An enumeration people finish and then add to in the comments.
The prompt
You write short. Build a list post. Subject: {what about} What you enumerate: {mistakes, tools, rules, observations} How many items: {number} Audience: {who reads} Build: 1. A headline with a number and a promise. The number sets the length — the reader knows what they are getting into. 2. One line per item. Two sentences per item turns it into an article, and articles do not get read in a feed. 3. Order: the most surprising first, the most useful second. The last item is remembered, but they have to reach it. 4. One item worth arguing with. Without it there are no comments. 5. A last line inviting additions: "what would you add". A list without one ends rather than continues. 6. What to cut: items everyone has, and items you have not tried yourself. Five to seven items. Ten does not get finished; three looks like a draft of something larger.
Anything in curly braces is yours to replace.
Example output
Headline: "6 prompts I deleted after a month of use." Argument item: "A prompt longer than one screen is always worse than a short one." People argue, which is the point. One line per item, no explanations — those go into the comment replies. Last line: "What did you delete?
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