WRT-12 · SEC. 05 Content & Writing

Repurpose One Post Into a Multi-Format Pack

Turn one long-form post into a thread, a LinkedIn post, and an email blurb, not chopped-up excerpts.

FORMAT: workflow
DIFFICULTY: intermediate
TIME: 20 min
TOOLS: universal
MODELS: any
COPIES: 0 so far

When to use this

You wrote one solid long-form piece and need it to also work as a thread, a LinkedIn post, and a short email teaser. A straight copy-paste-and-cut job never sounds native to any of them.

The pattern

Pastes as plain text

Step 1: Extract the core argument.
"State the single core argument of my post in one sentence, plus the
3 supporting points that prove it. Nothing else. First ask me to
paste the post, then wait. Don't start until you have it."

Step 2: Review the extraction. Correct it if the model picked a
secondary point over the actual main argument.

Step 3: Generate each format from the extraction, not the original post.
"Using the core argument and 3 supporting points from step 1, write
three separate pieces:
1. An X thread of 6-8 posts, each under 280 characters, one point per
   post, hook in post 1, no numbering like '1/8'. If I name a different
   platform or character limit, use that instead.
2. A LinkedIn post under 200 words: more context and personal framing
   than the thread, ends with a question that invites comments.
3. A 3-sentence email teaser that makes someone click through to the
   full post, doesn't give away the ending."

Step 4: Read each output against the original post to confirm no claim
got distorted or overstated in compression.

Real example output

Core argument (from Step 1): "Code review comments that ask questions produce better code than comments that issue commands, because commands get complied with instead of understood." Supporting points: commands trigger compliance not comprehension; questions force the author to defend or discover the flaw themselves; teams that switch to question-based review have fewer repeat mistakes.

Thread, post 1: "Your last review comment said 'use a Map here instead of nested loops.' The author changed it. They also didn't learn anything, and made the same mistake in the next PR."

LinkedIn post (opening): "I used to think good code review meant catching every issue before it merged. Then I noticed the same three engineers kept making the same three mistakes, no matter how many times I caught them..."

Email teaser: "Most 'improve your code review' advice is about catching more bugs. The teams with the fewest repeat mistakes are doing the opposite: catching fewer, but making sure the author actually understands why."

Why it works

Extracting the argument before drafting each format stops the model from anchoring on the original post's sentence structure and just trimming it, which is how you end up with a "thread" that's really six sequential excerpts. Rebuilding from the same core argument means all three pieces stay accurate to each other even though they read completely differently.

Related patterns

WRT-04Rewrite One Draft for a Different Audience or RegisterConvert an exec summary into a technical deep-dive (or the reverse) without rewriting from scratch.GRW-02Turn a Shipped Feature Into a Launch ThreadTurn what you just shipped into a structured hook-problem-solution-proof-CTA launch thread.WRT-07Generate and Rank Headline or Subject Line VariantsGet headline options that hook a specific reader trigger, ranked, not ten flavors of the same idea.