Weekly Linear cycle progress report
Every Monday, an active-cycle progress digest from Linear grouped by status, with at-risk and carried-over issues called out and linked back.
Mondays at 9:00 AMEngineering Emailed to you
Use this routine →Opens prefilled — review and save.
Works with
The instructions
Every Monday at 9am, produce a read-only progress report on our team's active Linear cycle. Do not create, edit, comment on, or otherwise modify any issue, project, or cycle — only read. 1. Pull the team's current (active) cycle from Linear and its issues. Note the cycle name/number and its start and end dates. 2. Group the active cycle's issues by workflow state into three buckets using each issue's state type: Completed, In progress (started), and Not started (backlog/unstarted). Report the count in each bucket, and the share completed so far. If the team uses estimates (story points), add a points rollup as a secondary line; if estimates aren't set, skip points and lead with issue counts. 3. Call out at-risk work and link each issue by its identifier (e.g. ENG-123) and URL: - Blocked: issues your team has flagged with a "Blocked" label. If the team has no such label, say "no Blocked label detected" rather than guessing. - Stalled: started/unstarted issues with no update in roughly the last 7 days (infer from each issue's last-updated time and, if helpful, latest comment). Show the assignee and how long it's been quiet. 4. Flag scope changes: surface issues that appear to have been added after the cycle started (infer from issue creation time relative to the cycle start), so scope creep is visible. Treat this as a flag, not an exact metric. 5. Read the previous cycle's completed issues and summarize, in one or two lines, what shipped last cycle and which unfinished issues carried over into the current one. 6. Email the report grouped by status, with the at-risk and scope-change sections clearly separated and every called-out issue linked. If the active cycle has no issues, or Linear returns nothing for a section, say so plainly instead of inventing data. If you can't determine the active cycle, report that clearly rather than guessing which cycle is current.
What a run emails you
Linear cycle progress — Cycle 24 (week of 29 Jun 2026) 62% complete: 18 of 29 issues done with 4 days left; 2 issues look at risk. Status - Completed: 18 (41 pts) - In progress: 7 (16 pts) - Not started: 4 (9 pts) At risk - Blocked (via Blocked label): ENG-412 "SSO token refresh loop" — Priya, blocked 5 days → linear.app/acme/issue/ENG-412 - Stalled (no update 8 days): ENG-389 "Billing webhook retries" — Marcus → linear.app/acme/issue/ENG-389 Scope added after cycle start - ENG-431 "Hotfix: export CSV encoding" added Wed (not in original scope) Last cycle (23): shipped 21 issues incl. the new onboarding flow; 3 carried over (ENG-356, ENG-377, ENG-381), all now in progress this cycle.
How it works - Attach your **Linear** connection — the agent reads your team's active cycle and its issues, plus supporting metadata (states, comments, the previous cycle). A read-only Linear API key is enough; it never creates, edits, or comments on anything. - It groups issues by their Linear workflow state (completed / started / not-started), then derives the at-risk signals: **Blocked** comes from your team's "Blocked" label (Linear has no native Blocked status), and **stalled** is inferred from how long an issue has gone without an update. - Keep **"Email me the result"** on to get the digest in your inbox every Monday — a status breakdown with at-risk and carried-over issues linked straight back to Linear.
Make it yours - Change the day or time (e.g. Friday wrap-up instead of Monday kickoff) by editing the schedule, or point it at a different team's cycle. - Tell the agent which label you use for blocked work, or how many days of silence should count as "stalled" (the default is about a week). - Ask it to add a points rollup if your team estimates, lead with carry-over risk, or include a short per-assignee breakdown of in-progress work. Your connections stay yours: tokens are encrypted at rest, and the agent only uses the access you grant.
Run “Weekly Linear cycle progress report” on autopilot
Copy it to your account, tweak the details, and it runs mondays at 9:00 am.
Use this routine →More Engineering templates
Product feedback triageEngineering
Each weekday, turn raw Discord feedback into a deduped, triaged list of issues worth filing in Linear.
Weekdays at 10:00 AM
Weekly Cloudflare docs & feature digestEngineering
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
Fridays at 9:00 AM
Weekly library version & migration digestEngineering
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.
Mondays at 8:00 AM
W
Weekly GitHub repo changelog digestEngineering
Every Thursday, ask DeepWiki what's new in the public GitHub repos you depend on — releases, breaking changes, and migration notes — emailed as a prioritized summary.
Thursdays at 9:00 AM