# Linear sprint check

Twice a week, posts which issues in your Linear cycle are slipping and what was added since it started.

Requires Linear, through Composio. Requires Slack, through Composio. Runs on a schedule. Can use GitHub, through Composio (optional).

## Install

No one has run this against real Linear, GitHub and Slack accounts through Composio yet. Its eval cases use stand-ins.

```sh
npx @parcha/agentrun template install github:Parcha-ai/agentrun-templates/templates/linear-sprint-check@242f29da8317fbe51d0cce4628bdb5ab61d7ccc9 --trust
```

Or open `<your AgentRun address>/#/templates/install?src=github%3AParcha-ai%2Fagentrun-templates%2Ftemplates%2Flinear-sprint-check%40242f29da8317fbe51d0cce4628bdb5ab61d7ccc9`. Pinned to commit 242f29da8317fbe51d0cce4628bdb5ab61d7ccc9.

## What it does

Twice a week, a Slack post on how your Linear team's current cycle is going. It lists the issues that are slipping (past their due date, stuck in progress, not started with half the cycle gone), the work added after the cycle started, and the issues whose linked GitHub pull request is waiting on a review or has gone quiet. Every line names the issue, who has it and why it's flagged, and things already flagged at the last check are collected on one line instead of repeated. It only reads Linear and GitHub. It posts on its own only if you pick Never for approvals at install; it stays held to your team and channel either way.

- Skill `sprint-check`: Check one Linear team's current cycle through Composio's Linear tools. Find the cycle, open the team's issues that are in it, flag the slipping ones, the scope added after the cycle started and the linked GitHub pull requests that wait on a review or went quiet, then post one Slack update. Reads only; the one write is the pinned Slack post. Use for the scheduled check and for "how is the sprint going".

## What starts it

- On a schedule: on the cron line 0 9 * * 1,4 (UTC), unless you pick another time when you install it.
- By hand, any time: from the console, the API or the CLI.

## Inputs

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `stale_days` | integer, 1 to 30 | no | The schedule passes your saved setting. Blank: 3. Example: `3`. |

### Setup, filled in once at install

| Name | Type | Required | What it is |
| --- | --- | --- | --- |
| `team_id` | string | yes | Your Linear team's ID, a UUID like 9cfb482a-81e3-4154-b5b9-2c805e70a02d as Linear's API and Composio's LINEAR\_LIST\_LINEAR\_TEAMS show it. Not the team key like ENG. |
| `channel` | string | yes | The Slack channel ID the check goes to, like C0123ABCD (in Slack: the channel's details, at the bottom). Not a #name. |
| `owner` | string | no | Optional: the GitHub account or organization that owns the repository your issues link pull requests from, like Parcha-ai. Leave it and repo out to skip the PR check. |
| `repo` | string | no | Optional: that repository's name without the owner, like agentrun. |
| `stale_days` | integer | no | How many days without an update makes an in-progress issue or an open linked PR stale; 3 unless you set it. Default: `3`. |
| `cron` | string, cron | no | When the check runs, as a cron line (minute hour day-of-month month day-of-week): Monday and Thursday 09:00 unless you set it. Default: `0 9 * * 1,4`. |
| `timezone` | string, timezone | no | The IANA time zone the cron line is read in (Europe/Madrid, America/New\_York): UTC unless you set it. Default: `UTC`. |

## What it needs

- Harness: pi, claude-agent, codex
- Model: balanced tier, low effort
- Tools: read
- Composio Linear tools: LINEAR_GET_CYCLES_BY_TEAM_ID, LINEAR_LIST_ISSUES_BY_TEAM_ID, LINEAR_GET_LINEAR_ISSUE. Reads your team's cycles and issues, and each cycle issue's details and links. The cycle and issue lists are held to the team you set; reading one issue can't be held to a team, so the agent only opens issues from your team's list. Writes nothing in Linear.
- Composio GitHub tools (optional): GITHUB_GET_A_PULL_REQUEST, GITHUB_LIST_REVIEWS_FOR_A_PULL_REQUEST. Reads the pull requests linked from your cycle's issues, in the one repository you set. Writes nothing on GitHub. Without it, or without a repository set, the PR check is skipped.
- Composio Slack tools: SLACK_SEND_MESSAGE. Posts the sprint check to the one Slack channel you set, and nowhere else.
- Computer: Wherever your AgentRun puts a new agent
- Keys: A model key
- Learning: on

## Sample output

Input:

```json
{
  "content": "Scheduled run. Check the team's current cycle with your sprint-check skill and post it.",
  "stale_days": 3
}
```

Output:

Illustrative output, written by hand from the `sprint-health` eval case's test team. A measured eval run replaces it.

Thursday's check of the Engineering team's Cycle 42, day 11 of 14. Three issues are slipping: one past its due date,
one with no update in nine days, one not started. One customer escalation came into the cycle on Nov 18. ENG-21's pull
request has waited a week for carol's first review. The backlog issue and the approved PR stayed out.

## Tested

Passes 4 of 4 eval cases on pi, 4 of 4 on Claude Code and 4 of 4 on Codex.

4 eval cases: injection-in-issue, no-repeats, on-track, sprint-health.

## Source

- Package: https://github.com/Parcha-ai/agentrun-templates/tree/242f29da8317fbe51d0cce4628bdb5ab61d7ccc9/templates/linear-sprint-check
- Publisher: Parcha-ai
- Author: Parcha Labs
- Version: 0.1.0
- License: Apache-2.0
- Category: Engineering
- Page: https://marketplace.agentrun.ai/templates/linear-sprint-check/
