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
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
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 like this
Build a RACI Chart from Your Project Task List with Ownership Gaps Flagged
Turns a pasted task list into a RACI table with one Accountable per task, flags unowned or over-consulted tasks, and lists questions to confirm with your team.
Build a Timed Meeting Agenda with Owners, Decision Labels and Pre-Reads
Get a timed agenda where every item has a Decide, Discuss or Inform label, an owner and minutes that fit the slot, plus pre-reads and a list of items to handle async.
Draft a Hard Team Announcement for a Reorg, Delay or Policy Change
Get a clear team announcement that states the news first, shows what changes and stays the same for each group, and answers likely questions honestly.
Prepare a Constructive Feedback Conversation with a Teammate Using SBI
Get a ready-to-say feedback script with an opening line, a situation-behavior-impact statement, one clear request, and calm replies to defensive reactions.
Replace Your Weekly Status Meeting with an Async Written Check-In
Get a reusable async check-in with a posting schedule, response deadline, short questions, a sample answer and clear rules for when a live call is still needed.
Run a Brainstorming Meeting That Ends with Chosen Ideas and Owners
You get a timed brainstorming agenda with silent ideation, clustering and dot voting, plus idea prompts, ending with top ideas, owners and a next test.