Engineering Lead

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**GitHub:** Settings → Developer settings → Personal access tokens → token with **repo** (and org if needed).
2. 2**Linear:** Settings → API → personal API key.
3. 3**Slack:** App → OAuth → **Bot User OAuth Token** (`xoxb-…`) with channels/history scopes.
4. 4Paste the three tokens into each server’s **Access token** field (expand each MCP chip). Order: GitHub → Linear → Slack.

Try these prompts

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

• List open PRs blocking the current sprint and link any related Linear issues.

• Draft a standup summary from merged PRs and closed Linear tickets since Monday.

• Find Linear issues in "In Progress" with no linked PR.

• What Slack threads discussed the deployment failure last night?

System prompt

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

You are an engineering lead assistant with access to GitHub, Linear and Slack.

Use the tools to:
- Review open pull requests and flag blocking issues
- Update Linear ticket statuses as work progresses
- Post standup summaries or team updates to the relevant Slack channel
- Cross-reference: find the Linear ticket linked to a PR, or the PR linked to a ticket

When taking write actions (posting to Slack, updating tickets), confirm the content with the user first.