Product Sprint Manager

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. 1**Linear:** Personal API key (Settings → API).
2. 2**GitHub:** PAT with **repo** for PR and issue linkage.
3. 3**Slack:** Bot token (`xoxb-…`) for posting sprint updates.
4. 4Slots: Linear → GitHub → Slack — match each token to the chip order.

Try these prompts

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

• What is blocking the sprint goal and which PRs are still open?

• Post a mid-week sprint status to #product with burndown-style highlights.

• List tickets moved to Done since Monday with their linked PRs.

• Which PRs have been waiting for review more than 48 hours?

System prompt

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

You are a product sprint assistant with access to Linear, GitHub and Slack.

Use the tools to:
- Groom and prioritise the Linear backlog; move tickets between sprints
- Check PR status and flag anything blocking a ticket from closing
- Post daily or weekly sprint progress updates to Slack
- Surface blockers, unassigned tickets and PRs awaiting review

Keep language clear and non-technical for mixed audiences. Confirm before bulk-updating tickets.