Write a Twitter thread from my source material and in my voice. The thread must make one useful, defensible point; do not invent facts, results, quotes, customer stories, or citations. Topic and point I want readers to take away: [TOPIC AND THESIS] Source notes, links, facts, and examples I can support: [SOURCE MATERIAL] My voice and examples of prior posts: [VOICE EXAMPLES] Target reader and desired action: [AUDIENCE AND ACTION]
Thread length and any required link or disclosure: [FORMAT REQUIREMENTS] First, state the thread's single-sentence thesis and propose three hook options. Each hook should create a specific reason to keep reading without false urgency, vague claims, or bait-and-switch framing. Then write the selected thread as numbered posts, with one idea per post and natural punctuation for the platform. Make the first post stand alone, develop the argument through examples or a sequence, and finish with a restrained takeaway or action that matches my goal. Use short posts, but vary rhythm so the thread does not read like clipped notes. Put attribution beside claims that come from a source, and use [VERIFY] where a statistic, quote, or detail needs confirmation. If a link is central, suggest where it belongs rather than repeating it. Do not stuff keywords, use engagement bait, or add a call to action unrelated to the thread. Return: 1) three hooks, 2) one complete thread, 3) an optional two-post shortened version, and 4) a pre-post checklist with factual, attribution, and voice checks. Before answering, verify that each post advances the thesis and flag claims unsupported by my source material. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [TOPIC AND THESIS] | State the topic and the one conclusion you want the thread to support. | Why weekly project updates fail; the thesis is that decision logs beat status summaries when a cross-functional team is moving quickly. |
| [SOURCE MATERIAL] | Paste your notes, links, data, examples, and any claims you have verified. | Notes from three internal product launches: update meetings repeated old information, while a shared decision log recorded owner, decision date, alternatives considered, and open question; no external statistics. |
| [VOICE EXAMPLES] | Paste a few posts you wrote or describe your preferred tone and sentence style. | Direct and practical. I start with a concrete observation, use short paragraphs, and avoid exaggerated claims or motivational language. |
| [AUDIENCE AND ACTION] | Describe the people you want to reach and the appropriate action you want them to take. | Product and operations leads; encourage them to try a decision-log template at their next planning meeting. |
| [FORMAT REQUIREMENTS] | Enter the desired number of posts, any link, disclosure, brand rule, or character constraint. | 8–10 posts; include a link placeholder in the final post; no hashtags; disclose that the examples come from my own team. |
How to use
- Start with source notes, not a topic alone, so the thread can make claims you can defend.
- Choose one hook that accurately reflects the thread's conclusion; rewrite it if the body cannot deliver on it.
- Read every post independently because readers may see it outside the full thread.
- For a follow-up, send: “Keep the thesis, but make this a six-post thread for founders and remove internal jargon.”
Variations
Thought leadership
Use this for an experience-based point of view without relying on external research.
Write a thought-leadership Twitter thread from my firsthand experience. Core lesson: [LESSON]. Specific experiences I can truthfully share: [EXPERIENCES]. Audience: [AUDIENCE]. Voice: [VOICE]. Produce 7–9 numbered posts: a concrete hook, the mistaken assumption, what I observed, the changed approach, and a practical takeaway. Do not present personal experience as universal evidence or imply results I cannot prove. Flag every broad claim that should be narrowed.
Research thread
Use this when explaining a report, article, or dataset with citations.
Turn this research into a careful Twitter thread. Source material and links: [SOURCES]. Central finding: [FINDING]. Audience: [AUDIENCE]. Thread length: [LENGTH]. Write numbered posts that distinguish reported findings, interpretation, and limitations. Attribute each numerical claim or quote in the same post, use exact figures only when supplied, and include a source link placement suggestion. Return the thread and a list of claims requiring verification before posting.
Launch thread
Use this to announce a product or feature without unsupported marketing claims.
Draft a Twitter launch thread for a product update. Product and change: [UPDATE]. User problem it addresses: [PROBLEM]. Demonstrable details: [EVIDENCE]. Target users: [AUDIENCE]. Desired action: [CTA]. Write 5–7 numbered posts covering the problem, what changed, how it works, constraints or availability, and the next step. Avoid claims such as “best,” “first,” or performance gains unless my evidence supports them. Check that the call to action matches the actual launch status.
Tips
- A thread needs one argument, not a collection of related observations; remove posts that do not prove, explain, or qualify the central point.
- Put the evidence close to the claim it supports, especially for numbers, customer outcomes, and quoted statements.
- Avoid splitting one sentence across several posts to inflate length; each post should still make sense in a timeline view.
- Keep a final factual pass separate from copy editing, because polished wording can make weak claims sound more certain than they are.
FAQ
How long should a Twitter thread be?
Use only as many posts as the idea needs. A focused six-post explanation usually performs better than a stretched sequence with repeated points.
Can AI match my Twitter voice?
It can approximate patterns from examples you provide, but you should edit the final thread for phrasing, opinions, and claims you would genuinely make.
Should every thread have a call to action?
No. Add one only when it follows naturally from the topic, such as reading a cited source, trying a process, or replying with a relevant experience.