Build a signal-over-noise weekly Slack announcement digest for your team
Turns a week of scattered Slack announcements into one tight, scannable weekly digest that respects signal over noise — the digest your team actually reads instead of mutes.
You are a senior internal-comms writer who runs high-signal team channels. People are drowning in pings; your job is to make one digest a week they actually read.
I will paste a week of raw Slack announcements (threaded or flat, messy is fine).
[RAW ANNOUNCEMENTS — paste messages, dates, channels, authors]
Team context:
- Team size and type: [E.G. '40 engineers, fully remote']
- Audience priority: [WHO MOST NEEDS THIS — e.g. 'ICs shipping a release Friday']
- This week's north star: [THE ONE THING THAT MATTERS MOST]
- Tone: [WARM / MATTER-OF-FACT / PLAYFUL]
- Channel norms: [E.G. 'threads over top-level posts', 'reactions not replies']
Produce the digest with these rules:
1. Signal over noise — keep only what changes someone's work this week or next. Drop status updates no one can act on. If you cut something, list it in a short 'Omitted (low signal)' footer so nothing disappears silently.
2. Group by what the reader needs to do, not by who posted: 'Action needed', 'FYI / heads-up', 'Wins & shipping'. Lead with the section that has deadlines.
3. Every item gets a one-line summary, a deadline or 'no deadline', and a link placeholder [LINK]. No item over two lines.
4. A top 'Read this first' line: the single most important thing in 15 words or fewer.
5. Plain language. No corporate filler ('excited to share', 'circle back'). No emojis unless I asked for playful.
6. Length cap: readable in under 90 seconds on mobile.
Rules:
- Do not invent deadlines. If an announcement lacks a date, mark it 'deadline TBD' and flag it.
- Do not soften or hide bad news (an incident, a delay). State it plainly with the mitigation.
- If the raw dump is thin or mostly noise, say so and produce a shorter 'quiet week' digest rather than padding it.
Output the ready-to-paste Slack message, then the omitted-footer.
Success signal: the output is good only if a teammate can read it in under 90 seconds, every action item has a deadline or 'TBD', and nothing important was silently dropped.Use case
Use when you run a busy team channel and want to ship a Friday digest people open instead of scroll past.
When to use this
End of the week, after collecting the raw announcements. Not for breaking or time-critical updates that need immediate posting.
Follow-up prompts
- Write a one-paragraph onboarding-friendly 'how we use this channel' blurb to pin alongside the digest.
- Build a 4-week template so I can run this digest as a recurring Friday habit.
- Draft a polite 'move this to a thread' reply for announcements that do not earn a digest slot.
- Source
- promptfork seed
- License
- CC-BY-4.0
- Published
- 6/22/2026