Social Media Thread
Write a multi-post social thread (X/Twitter, LinkedIn, Threads) that hooks, delivers, and converts: it first locks the single angle/big idea, the platform and its character limits, the target reader, and the CTA, then drafts the thread as numbered posts with a scroll-stopping hook, one idea per post, and a clear close. Covers Twitter thread, LinkedIn carousel copy, viral thread, social content, thought-leadership posts, and engagement hooks. Locking one angle and the hook before writing is the point: a small model that commits to a single big idea avoids the meandering thread that tries to say five things and stops no scroll.
Steps
Entry step: angle-scope. Each step names the specialist role it wants; the full working prompt is expandable.
- Angle scopeplannerentry
lock the one big idea, platform limits, reader, and CTA
Show working prompt
1) State the ONE big idea/angle in a single sentence — the single takeaway the reader keeps. 2) Pick the platform and its constraints (e.g. X: <=280 chars/post; LinkedIn: <=3000 chars, line breaks matter). 3) Define the target reader and why this angle stops their scroll. 4) Decide the thread length (e.g. 6-10 posts) and the CTA for the final post (follow, link, reply prompt). 5) Sketch the post-by-post beat list: hook → 1 idea per post → close/CTA. Write an acceptance-criteria checklist (e.g. 'post 1 is a standalone scroll-stopping hook'; 'one idea per post'; 'every post within the char limit'; 'numbered and ordered'; 'final post has a clear CTA'; 'on a single consistent voice'). Use write_task_note for the angle + beats + checklist, and write the same to the produces path. No thread copy yet.
- Draft the threadcopywriter
write the numbered thread to the locked angle and limits
Show working prompt
Write the full thread as numbered posts. 1) Post 1 is the HOOK: a standalone, curiosity- or tension-driven opener that works even if no one reads the rest — no 'a thread:' throat-clearing as the only content. 2) Each subsequent post delivers exactly one idea from the beat list, building the argument. 3) Keep every post within the platform's character limit (count characters). 4) Use a punchy, consistent voice; short lines; concrete specifics over abstractions. 5) The final post delivers the CTA. Output markdown as a numbered list where each item is one post, with a character count noted in parentheses after each. Save to the produces path and note total post count.
- Evaluatereviewer
Grade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
Show working prompt
Read social-thread.md and grade against the checklist. Check EACH and write PASS/FAIL: (a) post 1 is a standalone, scroll-stopping hook; (b) one idea per post; (c) every post is within the platform character limit (verify the counts); (d) posts are numbered and logically ordered; (e) the final post has a clear CTA; (f) a single consistent voice throughout. A thread that exceeds the char limit on any post or has a weak/missing hook FAILS — loop back to draft and name the posts to fix. Then route — this is the whole point of the loop: - **Every criterion PASSES →** call `advance_task_step({ ref, stepId: "evaluate", next: "finish" })`. - **Any criterion FAILS →** write the specific gaps to notes, then call `advance_task_step({ ref, stepId: "evaluate", next: "draft" })` to loop back. The builder fixes exactly those gaps. Never route to `finish` while any criterion is unmet. The build phase's completion gate already blocked a grossly-incomplete deliverable; your job is the judgment an automated check cannot make (does it actually work, read well, look right). After ~3 unproductive loops, stop and report DONE_WITH_CONCERNS so the user can step in. - Finishdeveloper
All acceptance criteria met. Stamp a short summary and report DONE.
Show working prompt
Every acceptance criterion passed. Write a one-paragraph DONE summary to task notes via `write_task_note`: what was built, the deliverable path(s), and a one-line confirmation that each criterion is met. Then report DONE.
Triggers
Phrases that suggest this craftbook to a crew.
- write a twitter thread
- social media thread
- linkedin post
- viral thread
- write social content
Source
View this craftbook on GitHub · MIT license