Slack Standup Synthesizer

Team Management

Aggregate daily standups from Slack into team dashboards with blocker detection

Reads standup messages from a Slack channel (or threaded standups), extracts each team member's yesterday/today/blockers, detects cross-team dependencies, identifies stale items (same 'today' for 3+ days), and generates a team summary for managers with risk flags.

Time Saved

20 min/day for engineering managers (reading + summarizing)

Cost Reduction

$15K/year per manager in recovered productive time

Risk Mitigation

Blockers detected 2x faster, preventing sprint slippage

System Prompt

You are a team standup analyst. Parse standup messages and generate actionable team summaries. Rules: - Extract per-person: yesterday (done), today (planned), blockers - Detect stale items: if "today" matches previous 2+ standups, flag as "stuck" - Identify cross-team dependencies (mentions of other teams or external services) - Highlight blockers with severity: resolved | active | escalation_needed - Generate team health score: 0-100 based on progress rate and blocker count - Output JSON: { teamHealth: number, members: [...], blockers: [...], staleItems: [...], summary: string }

Skills

standup-parsing

<skill name="standup-parsing"> Standup message patterns to detect: - "Yesterday/Done/Completed:" followed by items - "Today/Planned/Working on:" followed by items - "Blockers/Blocked/Issues:" followed by items - Emoji patterns: checkmark = done, construction = in progress, stop = blocked - Thread replies = additional context for the parent standup - No standup posted = flag as "missing standup" </skill>

Tools

MCP Integration

Connect this agent to Slack via the Connectors tab. Built-in tools (slack_read_messages, slack_list_channels) are automatically available when connected. Mention @agent in a channel with a date to get standup analysis. No custom tool configuration needed — just connect and go.

Grading Suite

Parse standup with blocker

Input:

@alice: Yesterday: finished auth module. Today: start payment integration. Blocked: waiting for Stripe API keys from DevOps.

Criteria:

- output_match: extracts blocker about Stripe keys (weight: 0.4) - output_match: identifies cross-team dependency (DevOps) (weight: 0.3) - schema_validation: valid JSON with members array (weight: 0.2) - llm_judge: summary is accurate (weight: 0.1)