Turn Rough Notes into a Weekly Slack Team Update with Clear Blockers

Turns your messy weekly notes into a Slack-ready team update under 150 words, split into Shipped, Next and Blocked, with an owner and date for every blocker.

Prompt

Prompt
Act as a team lead who writes short Slack updates that people actually read.

I will paste my raw notes for the week right after this prompt. Turn them into one weekly team update I can post in Slack.

Rules:
1. Keep the whole update under 150 words. Cut anything a teammate would not act on or ask about.
2. Every Shipped item states the result (a number, who it helps, or what changed for users), not just the activity.
3. Every Blocked item names the blocker, the person or team who can unblock it, and the date it is needed by. If my notes do not say who or when, write "Owner: ?" or "By: ?" instead of guessing.
4. Every Next item starts with a verb and names an owner.
5. Use Slack formatting: single-asterisk bold for section labels, plain bullets, no # headings, at most one emoji per section.

Output format:
*Weekly update – week of (date from my notes)*
*Shipped* – 3 to 5 bullets
*Next* – 3 to 5 bullets
*Blocked* – bullets written as: blocker – who can unblock – by when
Then, below a divider line, a section called "Gaps to check": anything vague, missing owners or dates, and any items you dropped and why.

Do not add work, numbers or names that are not in my notes; flag anything you had to assume.

Example output

Example for: a 5-person mobile app team lead pasting messy notes for the week of March 10.

Weekly update – week of Mar 10

Shipped ✅

  • Dark mode live on iOS and Android; 18% of active users turned it on in 3 days
  • Checkout crash fix (v4.2.1) out; crash rate down from 1.9% to 0.4%
  • Push notification opt-in screen redesigned; A/B test running through Mar 21

Next 🛠️

  • Finish offline cart sync – Priya
  • Draft Q2 accessibility audit plan – Marco
  • Review A/B results and pick a winner – Dana
  • Start Android 15 compatibility testing – Owner: ?

Blocked 🚧

  • Payment SDK upgrade needs new API keys – Finance ops (Leo) – by Mar 18
  • Offline sync design sign-off – Design (Hana) – By: ?
  • App Store screenshots need final copy – Marketing – by Mar 19

Gaps to check

  • Android 15 testing: your notes say "someone should start this" but name no owner. Assign one before posting or leave the "?" so the team sees it.
  • Design sign-off: no date given. If sync work stalls without it, add the date Priya needs it by.
  • Marketing blocker: notes say "marketing" only. Naming one person makes it more likely to get handled.
  • Dropped: the note about the team lunch and the long thread on renaming the staging server. Neither needs action from the channel.
  • Assumed: "crash rate" refers to the Firebase dashboard figure in your notes, not App Store data. Correct it if you use a different source.
  • Word count: message body is 118 words, leaving room to add one owner or a short link to the A/B test dashboard.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • The 150-word cap forces cutting low-value items, so the update gets read in Slack instead of skimmed past.
  • Requiring who can unblock and by when turns blockers into requests someone can act on, not just complaints.
  • Writing "?" instead of guessing, plus the Gaps list, shows missing owners before you post rather than hiding them.

Use on Friday or Monday when you have scattered notes, standup bullets or a ticket list. Paste them right after the prompt in ChatGPT, Claude or Gemini; rough fragments are fine.

Common edits

  • Change the word cap to 80 for a leadership channel or remove emojis for a more formal workspace.
  • Add a fourth section such as "Kudos" or "Metrics" if your team tracks wins or KPIs weekly.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity