Example output
#weekly-recap
Slack Weekly RecapAPPToday
Weekly Recap: Jul 4
Shipped
—Checkout rewrite is live; the one-click upgrade path removed the confirm step.
—New onboarding emails went out to 1,200 signups.
Blockers
—An E2B warm-pool flake blocked two deploys; the fix is in review.
—Waiting on legal for the partner MSA redline.
Next week
—Ship the workspace analytics tab.
—Close the two pilot conversions and start their onboarding.
What this delivers
Give a team a consistent Friday recap without chasing everyone for updates.
Turn a week of work into three skimmable sections in seconds.
Keep a lightweight paper trail of what shipped, what is blocked, and what is next.
Draft the recap once and paste it into any Slack channel.
Overview
Every Friday afternoon, Slack Weekly Recap drafts a short, paste-ready update for a team channel so nobody has to remember what shipped. It organizes the week into three tight sections, Shipped, Blockers, and Next week, each a couple of crisp bullets, in the tone of a Slack post rather than a status report. Point it at a channel topic and it frames the recap around that. The output is markdown you can drop straight into Slack, with no integration required to try it.
What you provide
channel_topictextUnder the hood
The worker's instructions and configuration
Install with an agent
Give this to your coding agent. It sets you up first via the onboarding prompt, then imports this template and keeps the first run in preview mode.
Set up Floom in my coding agent, then add this worker. First, read https://floom.dev/onboard and follow it to install Floom and sign me in. Import this Floom worker template into my workspace and keep it in test mode first: