Sprint Retro · Linear, Calendar & Slack

What you can do

A few things this template does well out of the box.

• Generate end-of-sprint summaries from Linear data + calendar ceremonies
• Identify carried-over issues and recurring blockers across sprints
• Post formatted retro summaries with wins, themes and action items to Slack
• Compare velocity and completion rates against previous sprints

How it works

Three steps to go from template to a live chat.

MCP servers used

The endpoints this template connects to by default. You can swap any of them in Agent Studio.

Getting your access token

A quick walkthrough for the credential this template needs.

1. 1Google Cloud Console → create OAuth 2.0 credentials for Calendar read access.
2. 2Linear → **Settings** → **API** → create a personal API key with access to your team's projects.
3. 3Slack → **api.slack.com** → your app → **OAuth** → copy the Bot User token.

Try these prompts

Copy one into the studio to see the agent in action.

• Sprint 14 just ended. Pull all completed and carried-over issues from Linear, check what retro meetings are on the calendar, and draft a summary for #engineering on Slack.

• What did the team ship this sprint? Compare it to what was planned at the start.

• Identify the top 3 blockers from this sprint based on Linear issue comments and Slack threads in #engineering.

• Generate a retro doc: what went well, what didn't, and 3 action items. Post it to Slack before tomorrow's retro meeting.

System prompt

The default instructions the model starts with. Edit it any time inside Agent Studio.

You are a sprint operations assistant connected to Google Calendar, Linear and Slack.

Use the available tools to:
- Read sprint ceremony events (planning, standup, retro) from Google Calendar
- Pull completed, in-progress and carried-over issues from Linear for the current or recent sprint
- Analyse velocity, blockers and themes across the sprint
- Post structured retro summaries to Slack with: what shipped, what carried over, blockers, wins, and action items

Format retro summaries with clear sections. Include issue counts and highlight patterns (e.g. "3 of 5 blockers were CI-related"). Confirm channel before posting.