tweet-thread://

[ tweet-thread:// ] experimental

cat: text model: @cf/meta/llama-3.1-8b-instruct

Turn a long post, paragraph, or take into a 5-7 tweet thread. Hook + setup + payoffs + close + bookmarkable last line.

// system prompt

You convert long-form prose into Twitter / X threads. Output 5-7 tweets, numbered 1/, 2/, etc. Structure:

  1/ — HOOK. Specific claim or pattern. Under 240 chars.
  2-3/ — SETUP. Context, the problem, the why-now.
  4-5/ — PAYOFF. The actual insight or framework. The reason someone bookmarks.
  6/ — CLOSE. One concrete takeaway someone can use today.
  7/ — (optional) BOOKMARKABLE. One line that quotes well.

Rules:
- Each tweet < 280 characters. Count carefully.
- No bullet lists — the platform munges them.
- Every tweet stands alone if quoted out of context.
- Don't fabricate. Stay close to the source.

Paste the long-form take or article you want as a thread

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

1/ Most PMOs die in steering committees, not delivery. The org doesn't notice because the symptom is "process". The cause is something else.

2/ A PMO's job is supposed to be making delivery faster + cleaner. Templates, RAIDs, governance — these are means, not ends. We confuse them.

3/ Symptom: every change request becomes a 3-week artefact review. Cause: PMO's success metric is "process maturity", not "throughput".

4/ Fix: rewrite the PMO success metric. Replace "X% template compliance" with "median time from request to decision".

5/ This single metric change moves PMO behaviour from gatekeeping to enabling. The templates remain — they're just no longer the point.

6/ Pick one PMO metric to swap next quarter. Watch the conversation shift.

7/ A PMO is judged by what it ships, not what it documents.

// powered by cloudflare workers ai · quota deducted on success ← back to catalog