---
title: "Scrum Master recipe for Slack and Telegram | Agent Barn"
canonical: "https://agentbarn.dev/recipes/scrum-master/platform"
updatedDate: "2026-08-29T16:41:32.000Z"
author: Agent Barn
description: "Runs sprint ceremonies, tracks blockers, and keeps the team on cadence in Slack. Set it up on Slack or Telegram with Agent Barn."
tags: [Team cadence, AI agents, workflow automation]
categories: [Recipes]
---

# Scrum Master recipe for Slack and Telegram

A coordination teammate that collects stand-up updates, reminds people about pending tasks, and summarizes sprint progress.

## Choose a platform

### Slack

**The whole team.** Runs standups and posts summaries in a channel, which is where a ceremony involving several people belongs.

Choose for any team cadence, since the agent needs to reach and hear from everyone.

### Telegram

**One coordinator.** Delivers the same sprint summaries to a single chat, without prompting the rest of the team.

Choose only when one coordinator wants the reporting privately, not a team ceremony.

## Recipe overview

- Category: Team cadence
- Tools: Jira + Slack
- Trigger: A scheduled ceremony, configured work-item change, or stand-up window.

## Workflow

1. **Collect updates:** Ask for stand-up updates or read configured project activity.
2. **Track blockers:** Identify pending work and blockers from the available context.
3. **Prepare summary:** Create a concise update for the team’s agreed cadence.
4. **Keep moving:** Post reminders and the sprint summary in Slack.

## Initial setup

1. **Template:** Ceremony cadence, question format, and summary structure.
2. **Skills:** Jira access for the relevant project or sprint information.
3. **Policies:** The Slack channels and direct-message rules for the team.

## Integrations

### Jira

Read sprint, issue, assignee, status, and blocker information for the configured team.

- Requirement: required
- Credential: An Atlassian account email, site URL, and scoped or non-scoped API token.

#### Permissions

- Projects and boards: read
- Issues and sprint state: read
- Comments or updates: omit unless the team explicitly enables them

#### Setup

1. Select the board, project, and active sprint sources.
2. Keep write actions disabled for the initial coordination pilot.
3. Validate summaries against the board before automating reminders.

## Human review

Keep the agent focused on coordination and summaries; the team retains ownership of commitments, priorities, and delivery decisions.