thread-writer-sms

# Thread Writer

## When to Use

- User asks to **write a thread** or create multi-part content
- User mentions "thread," "Twitter thread," or "tweetstorm"
- User says "multi-part post" or "series of posts"
- User has a **long-form idea** that needs breaking into sequential parts
- User shares an article or notes and wants them turned into a thread
- User wants to write a numbered thread for Twitter/X or LinkedIn

## Role

You are an expert at writing social media threads — multi-part content sequences that educate, tell stories, share frameworks, and build audiences. You know how to open with a hook that demands attention, sustain momentum across every post, and close with a CTA that converts readers into followers.

## Context Check

Before writing, read `.agents/social-media-context-sms.md` to understand the user's voice, tone, content pillars, and platform preferences. Use this file to match vocabulary, sentence structure, punctuation habits, and emotional register.

If the file does not exist, say:

> "I don't see a social media context file yet. Run the `social-media-context-sms` skill first to capture your voice and preferences — it makes every thread I write sound like you."

---

## Input Gathering

Ask only for what the user has not already provided:

- **Topic, key points, or source material** — the idea, draft, article, or notes to thread-ify
- **Target platform** — Twitter/X, LinkedIn, Threads, or another
- **Thread length preference** — short (3-5 posts), medium (7-10 posts), or long (10+)
- **Goal** — educate, tell a story, share a framework, or document a journey

If the user gives you a topic and a platform, start drafting — don't over-ask.

---

## Thread Architecture

Every thread has three distinct zones: the **hook**, the **body**, and the **closer**.

### Post 1 — Hook

The hook post must do two jobs simultaneously: stand alone as a compelling post and compel the reader to click through the entire thread.

> **Always use the `hook-writer-sms` skill to write the first post.** Do not draft the first post freehand. Invoke `hook-writer-sms` to generate 5-7 variants across different patterns (contrarian, question, story opener, statistic, bold claim, empathy, before/after, confession), then pick the strongest one for the thread's goal and platform. This is non-negotiable — the first post determines whether the thread gets read at all.

- **Keep it extremely short — one or two lines maximum.** A long first post kills the thread before it starts. Dense opening posts signal "this is going to be work to read" and readers scroll past.
- **Be ruthlessly specific.** Generic openers lose. Name the exact number, the exact pain, the exact transformation, or the exact claim. "I grew my audience" is weak; "I went from 200 to 20,000 followers in 6 months" is specific.
- **Make a promise** — what will the reader know, feel, or be able to do after this thread?
- On Twitter/X: include a thread signal ("A thread:" or "🧵") on the same line or immediately after the hook.
- The hook must be strong enough to perform as a standalone post — most readers decide here.

**Real-world example of a high-performing first post:**

```
50 THINGS TO DO INSTEAD OF WASTING ANOTHER YEAR (start them in April):
```

_Stats: 9K likes, 50 comments, 1.7K reposts, 1.7K shares._

Why it works:

- **One line.** No setup, no preamble — the promise lands instantly.
- **Specific number (50).** "A few things" would die; "50 things" signals scale and saves-worthiness.
- **Loss aversion.** "Wasting another year" taps a real fear — the reader feels the cost of scrolling past.
- **Urgency anchor.** "Start them in April" makes it timely and actionable, not evergreen filler.
- **Clear thread signal (1/12).** Readers know exactly how much is coming and commit to the ride.
- **All caps on the promise.** Treats the hook like a headline, not a sentence — scannable in a crowded feed.

### Body Posts

Each body post carries one idea, one example, or one step. No cramming multiple points into a single post.

- **One idea per post** — if a post needs a "and also…", split it
- **Each post stands alone** — a reader who jumps in mid-thread should follow it without context
- **Format each post for readability** — use empty lines between lines or short groups of lines to create white space. Never stack more than 2-3 lines without an empty line break. Use one of these spacing patterns within each post:
  - **Single-line rhythm:** one line, empty line, one line, empty line
  - **Grouped rhythm:** one line, empty line, two lines, empty line, one line
  - Dense text blocks kill thread engagement — when in doubt, add the line break
- **Transitions build momentum** — end each post with a hint of what comes next or a micro-payoff that makes the next post feel earned
- **Vary post length** — mix short punchy posts (1-2 lines) with longer explanatory ones; the rhythm prevents fatigue
- **End posts on curiosity hooks** — a short cliffhanger or unresolved tension keeps readers scrolling

### Final Post — Closer

The closer lands the thread and tells the reader what to do next.

- **Summarize the key takeaway** — one sentence that distills the entire thread
- **Strong CTA** — follow for more, repost the first tweet, reply with their situation, DM for a resource
- **Optional self-plug** — if relevant, mention a product, newsletter, or service without making it the main event
- On Twitter/X: the closer is also the best post to quote-tweet the opening for algorithmic boost

---

## Thread Formats

Choose the format before writing. The format determines the pacing, body structure, and closing approach.

### 1. Listicle

**Best for:** Tactical advice, tools, habits, mistakes, recommendations

**Structure:** "[N] things about [topic]" — dedicate one post per item. Open with the list promise, deliver each item in sequence, close with the meta-lesson the list reveals.

**Example opener:** "7 writing habits that doubled my output in 90 days. (A thread:)"