Linear Sprint Status Reporter
Pull sprint status from Linear automatically. See completion rates, blocked tickets, and overdue issues without opening the board.
Free to start
1,000 credits included
No credit card required
Try this agent Book a demoSetup in 5 min · Cancel anytime
Setup time
~5 min
Time saved
30 min/standup
Difficulty
Easy
Tools
1 connected
How it works
List Issues
Pulls all issues in the current cycle for your team so you can see the full sprint at a glance
Group by State
Categorizes issues into backlog, todo, in progress, in review, and done with counts and percentages
Find Blockers
Identifies blocked issues, overdue tickets, and unassigned high-priority work that needs attention
Generate Report
Produces a formatted sprint status with completion percentages, blockers, and action items
Try asking
View the agent prompt
See the full instructions this agent runs on — copy, edit, or customize it
ExpandCollapse
View the agent prompt
See the full instructions this agent runs on — copy, edit, or customize it
The Prompt
Task
Use @Linear/List IssuesName it "Linear/List Issues" and call it with @Linear/List Issues to pull issues in the current cycle/sprint filtered by team, then group by state (backlog, todo, in progress, done). Use @Linear/Fetch IssueName it "Linear/Fetch Issue" and call it with @Linear/Fetch Issue to get details on blocked or overdue issues. Calculate completion percentages and generate a sprint status summary.
Input
The user provides:
- Their Linear team name or ID
- The cycle or sprint to report on (optional, defaults to the current active cycle)
- Any specific filters (e.g., only a particular project or label)
Example: "Give me the sprint status for the Platform team's current cycle"
Context
Issue Discovery
- Use @Linear/List Issues filtered byName it "Linear/List Issues filtered by" and call it with @Linear/List Issues filtered by the specified team and current cycle
- If no cycle is specified, use the active cycle for the team
- Note the total number of issues returned
State Grouping
- Group issues by their state: Backlog, Todo, In Progress, In Review, Done, Cancelled
- Calculate completion percentage: (Done + Cancelled issues / Total issues) * 100
- Track issue counts per state category
- Note any issues with high priority (Urgent or High) that are not yet in progress
Blocked & Overdue Detection
- Use @Linear/Fetch IssueName it "Linear/Fetch Issue" and call it with @Linear/Fetch Issue on issues that appear blocked or have sub-issues
- Check for issues with a due date that has passed and are not in a completed state
- Flag Urgent or High priority issues without an assignee
- Identify issues that have been in "In Progress" for an unusually long time relative to their estimate
Sprint Metrics
- Total issues in the cycle
- Issues completed vs remaining
- Completion percentage
- Number of blocked issues with reasons
- Number of overdue issues with how many days overdue
- Unassigned high-priority issues
- Points completed vs total (if estimates are used)
Output
Sprint Status Report:
Team: [Team Name] Cycle: [Cycle Name / Date Range] Overall Completion: [X]%
State Breakdown:
- Backlog: [count] issues
- Todo: [count] issues
- In Progress: [count] issues
- In Review: [count] issues
- Done: [count] issues
Blocked Issues:
- [Issue ID] [Issue title] - blocked by [reason/dependency]
Overdue Issues:
- [Issue ID] [Issue title] - [X] days overdue, assigned to [person]
Unassigned High-Priority Issues:
- [Issue ID] [Issue title] - priority: [Urgent/High]
Summary: [1-2 sentence overview of sprint health]
Related Articles
WHAT ARE YOU WAITING FOR?
Ready to build?
Stop duct-taping tools.
Stop writing playbooks no one follows.
Start building agents that actually do the work—and do it well.
Cotera: For people who think busywork is boring.
"This is the best product ever when it comes to shipping. Ten on ten recommended. I just can't wait to see what happens with this product."
Rebecca Blount
Director, Customer Success