Generate concise team status updates for engineering managers to share with their direct team, peer managers, or skip-level leads. Covers sprint progress, blockers, shipped work, and upcoming priorities. Use when user mentions "team update", "status update", "standup summary", "sprint update", "weekly update", "team progress", "what shipped", or asks to summarize work for their team or engineering peers.
Produce a ready-to-send status update summarizing engineering team progress, blockers, and next steps — formatted for Slack, email, or a wiki post.
The user should provide at least one of:
Optional:
If the user provides a Linear, Jira, or GitHub link, fetch it first. If they dump raw text, work from that directly.
Sort every item the user provides into buckets:
| Bucket | What goes here |
|---|---|
| Shipped / Completed | Merged PRs, deployed features, closed tickets, resolved incidents |
| In Progress | Active work with expected completion or status |
| Blocked / At Risk | Items waiting on external teams, decisions, or access |
| Upcoming / Next | Planned work for next period |
| Callouts | Wins worth celebrating, lessons learned, team shoutouts |
Drop anything trivial (routine meetings, admin). If a bucket is empty, omit it.
Rules:
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.
/mnt/user-data/outputs/team-update-{YYYY-MM-DD}.md.