Standup digest

Standup digest

Turns a day's async standup posts into a 30-second read.

Workflow

1. Identify the channel and date

From $ARGUMENTS:

• Channel: default #standup or whatever the team uses — check team-core CLAUDE.md or ask.
• Date: default today; accept "yesterday", a weekday, or YYYY-MM-DD.

2. Pull

Use the Slack MCP to get messages in the channel for that date. Filter to:

• Top-level messages (not thread replies unless the top-level was a skeleton and the content is in the thread)
• Messages from team members (skip bots and external users)

3. Parse

Each standup post usually has:

• What I did yesterday / since last standup
• What I'm doing today / next
• Any blockers

Don't require a strict format. Extract signal from free-form posts. If someone wrote a wall of text, condense to 1-2 lines per section.

4. Output

# Standup — <date>

**Posted:** N of M  ·  **Blocked:** N  ·  **No post:** <list names>

## Shipping today
- **<person>:** <one line of what they're working on>

## Blocked / needs help
- **<person>:** <blocker, one line> — <who they tagged or "no owner yet">

## Shipped yesterday
- **<person>:** <one line>

## Didn't post
- <name>, <name>

Extraction rules:

• If a person listed 5 items for today, pick the one that'll move the most — or ask the user if it's truly unclear.
• "Blockers: none" → don't include them in the blocked section. Obvious but worth saying.
• If someone says "still working on X" three days in a row, flag that gently at the bottom ("X has been in flight for 3+ days").

Don't

• Don't post the digest back to Slack unless asked — this skill is read-only by default.
• Don't fabricate a post for someone who didn't post. Listing them in "Didn't post" is the whole point.
• Don't judge. If someone's "stuck" three days running, surface it — don't narrate why.