Team Status Update

1. Parse and categorize

Sort every item the user provides into buckets:

Drop anything trivial (routine meetings, admin). If a bucket is empty, omit it.

2. Write the update

Rules:

• Lead with impact, not task names. "Launched real-time notifications for 12K users" beats "Closed PROJ-412."
• Keep each item to one line. Two lines max if context is critical.
• Quantify where possible. Percentages, user counts, latency numbers, deploy dates.
• Name blockers concretely. Who/what is blocking, what's needed to unblock, and a proposed next step.
• Use plain language. Avoid jargon that doesn't add precision.
• Bold the key noun or metric in each line for scannability.

3. Format for channel

Slack (default):

*🚀 [Team/Project] — Week of [date]*

*Shipped*
• Item one
• Item two

*In Progress*
• Item (ETA: date)

*Blocked*
• 🔴 Item — waiting on [who/what]. Next step: [action].

*Up Next*
• Item

*Callouts*
• 🎉 Shoutout or win

Email: Subject line + same structure, no emoji, slightly longer sentences.

Wiki/Confluence: Use headings instead of bold, add ticket links inline.

4. Deliver

• If the user asked for Slack format, output as a single copy-pasteable block.
• If email, use the message_compose tool.
• If markdown/wiki, save to /mnt/user-data/outputs/team-update-{YYYY-MM-DD}.md.

Behavioral rules

• Never invent work the user didn't mention. If the input is thin, ask for more before guessing.
• If the user says "just clean this up," reshape their raw notes without adding substance.
• Default to concise. A good team update is 8–15 lines, not a novel.
• If blockers are present, always include a proposed next step — don't just list the problem.
• Adapt emoji and tone to audience: casual for team, minimal for skip-level.