Meetings & notes21 categories
Compress an update into a chat message
When the status belongs in Slack, not in a document nobody opens.
Compress the update below into a message for a team chat channel. Rules: 1. Under 120 words. The first line must work as a standalone preview. 2. Lead with the conclusion or the change, not with the process that produced it. 3. One short paragraph or at most four bullets. No nested bullets. 4. Be explicit about what, if anything, you need from the reader, and by when. If nothing, say "no action needed". 5. No hedging phrases: sort of, hopefully, I think we might, just wanted to flag. 6. If something is late or broken, say it in the first line rather than burying it. Then give me a one-line thread reply version for people who want the detail. Update:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Updates and follow-ups. The message after the meeting: status for a manager, a team update, and chasing what stalled.
Related prompts
Chase actions nobody clearly ownsA week after a meeting, when half the actions have quietly not happened.Summarise a week of standupsTurning daily noise into something a stakeholder can read on Friday.Write a weekly update for my managerFriday afternoon, summarising a week you can barely remember.Turn this into a team updateNotes that need to become a message people will actually read.One-line statusA stakeholder asks how it is going and wants the honest one-liner.Write the follow-up messageThe message you send an hour after the meeting to make it stick.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free