Standup brief

Standup brief

Build a compact morning brief. Aim for 10 lines or less. The user skims this in 30 seconds.

Inputs to gather (in parallel)

1. Calendar (Google Workspace MCP) — events for $ARGUMENTS (default: today). Include time, title, attendees (count only if >3), and whether the user is organizer.
2. Slack (Slack MCP) — unread mentions and DMs from the last 16 hours. Surface the top 5 by signal: direct mentions from teammates, unresolved threads the user is part of, explicit asks.
3. Notion (Notion MCP) — open action items assigned to the user across the workspace. Look in the team's task databases. Sort by due date ascending.

If an MCP isn't connected, say so in its section and continue — don't fabricate.

Output format

# <today's date, e.g. Wed Apr 22>

## Calendar (N events)
- HH:MM–HH:MM  <title>  <optional: • you're organizer>
- ...

## Slack — needs reply (N)
- @<person> in #<channel>: <one-line summary>  [link]
- ...

## Notion — due today/overdue (N)
- <task title> — due <date> — <project>  [link]
- ...

## Top focus
<One sentence: given the above, what should the user do first? Pick the item that's most time-sensitive or highest leverage. If nothing's urgent, say "clear morning — pick deep work.">

Rules

• If there are no items in a section, write "Nothing." — don't omit the header.
• Don't include routine standing meetings (1:1s, weekly reviews) in "Top focus" unless they require prep.
• Don't summarize Slack threads more than one line each. If a thread needs more context, link it, don't quote it.
• Never reply to Slack or accept/decline meetings automatically. This skill is read-only. Outbound actions go through /team-core:draft-email or a dedicated skill.