How to Rewrite a Rambling Status Update Into Three Lines

Anyone dumping a Slack or standup paragraph can rewrite it into a three-line status update in 10 minutes: what moved, what is stuck, and what happens next. Run it in ChatGPT, Claude, or Gemini before "just circling back" becomes the update.

A three-line status update is a report, not a diary. If the page still sounds like the standup, you never updated anyone. Three labeled lines tell one person what changed. A recap of the vibe tells no one.

This is not a three-bullet ask from a long DM. An ask is a request you typed to get work. This skill is a report on work already moving. It is not a five-line meeting recap email. A recap is after chairs. A status is one person, mid-week. It is not a WhatsApp voice note into a six-line brief. That brief starts as speech you did not write. This starts as a paragraph you already typed. Save the three-line shape as a skill prompt you can rerun.

Rewrite a three-line status update from a ramble

1. Paste the ramble. Do not draft a recap

Instruct ChatGPT, Claude, or Gemini: "Do not draft a status yet. Paste back the paragraph I give you. If a sentence has no fact, write UNKNOWN on that sentence. No cleanup. No smarter phrasing. No hello."

Paste the Slack dump, the standup note, or the email you were about to send. A model that "fixes" ums into a strategy is lying on your behalf.

Write three facts on paper before the three lines: who is reporting, which project noun they kept repeating, and whether a weekday appears. If you cannot name those three, read the ramble again. A 12-sentence loop is still one update.

Banned: circling back, just a quick update, hope this helps, as discussed, FYI for visibility, making good progress, on track, no real blockers except, the vibe was, I'll keep you posted, moving the needle, alignment, happy to sync, per my last.

2. Name the fact that moved, then the clock

Send the ramble back. Instruct: "Line one is Fact: one verb plus one object from the paste, plus a weekday I can see. If I named no fact, write UNKNOWN and stop. Do not open on I wanted to share."

Good fact: "Fact: vendor CSV with tax column reached finance, Tue 25 Aug." Bad: "Fact: making good progress on the file." Progress is a vibe.

If the ramble named two facts, keep the one with a weekday. Put the other on a second update. Do not nest it in Blocker.

If there is no weekday, write UNKNOWN on the date half of Fact. Do not invent Tuesday so the line looks finished.

3. Blocker, then Next. NONE is a legal word

Instruct: "Line two is Blocker: the one stuck noun the paste named, or NONE. Line three is Next: one verb, one object, one weekday from the paste. If I named no next, write UNKNOWN. Do not invent a risk. Do not invent Thursday."

Good blocker: "Blocker: tax column is blank on 14 rows." Bad: "Blocker: no real blockers except we should stay aligned." Aligned is a meeting you just scheduled in a status.

Good next: "Next: Maya sends the 14-row fix Thursday 27 Aug before 16:00 WIB." Bad: "Next: I'll keep you posted as things evolve." Evolve is a shrug.

Good none: "Blocker: NONE." Bad: "Blocker: none, though we should keep an eye on vendor mood." Mood is how a clean update grows a fourth line.

4. Force three lines, then stop the model

Hard cap: three lines. No greeting. No sign-off. No ramble pasted under the labels.

Tell the model: "Output exactly three lines labeled Fact, Blocker, Next. No fourth line. No Happy to discuss. No let's jump on a call. No bullet novel under Blocker. If a banned phrase appears, rewrite that line only."

ChatGPT will add a hello and a "hope this helps." Claude will hedge the fact into a suggestion. Gemini will turn the date into "later this week" and invent a blocker so the card looks finished. Cut all three.

If a fourth line appears, delete it. If Blocker is a paragraph because the model wanted to be thorough, you failed the job. Thorough is the ramble you already had.

If Next is empty because the model wanted a clean card, write UNKNOWN. A fake Thursday is a lie you told the channel.

5. One human pass as the person who was not in the room

Read the three lines as if you missed standup and have to act in the next hour.

Check three traps:

• A fact that is actually a feeling. "Team is aligned on the CSV" is not a fact. "Vendor CSV with tax reached finance, Tue 25 Aug" is.
• A blocker that is a meeting invite, or a next that does not exist on a calendar.
• A none the model filled with a risk so the card would look complete.

Fix those in your own words from the ramble. Then send the edited three back: "Replace only the words I changed. Do not re-expand. Do not add a recap."

One pass. Paste into Slack, the standup thread, or the ticket. If a paragraph still sits above the three lines, you never updated. Stop.

Reusable skill card

Trigger: You are about to paste a Slack dump and type "summarize this for the channel" or "write a quick status."

Input: The ramble, the project noun, one weekday if it exists, plus the banned-phrase list.

Output: Three lines labeled Fact, Blocker, Next. No greeting. NONE if nothing is stuck. UNKNOWN where a field was not in the paste.

Stop: After one human pass as the person who was not in the room. No fourth line. No invented date. No second fact hiding in Blocker. No ramble under the labels.

Takeaways

• Three lines: fact, blocker, next. Then send.
• A ramble is source. A three-line status update is a report. Do not ship both.
• NONE on the blocker is better than no real blockers except. UNKNOWN on the next is better than I'll keep you posted.
• Two facts is two updates. A hedge is Unknown, not a pick.