Weekly Linear Cycle Report

Every Friday the agent pulls the current cycle data — shipped, in-progress, backlog — computes velocity, flags slippage, and delivers a founder-friendly report on WhatsApp.

Cron + WhatsApp DMcyclesreportingvelocity

Conversation example

Cron triggered: Linear cycle report (Friday 4:30 PM)
http_request → Linear GraphQL (cycle + issues)

Pulling Cycle 32 data from the Engineering team...

Cycle 32 Report — April 8 → April 12 Scope: 47 issues (84 estimated points) Done: 38 issues (69 points, 82% completion) In Progress: 5 issues (10 points) Not Started: 4 issues (5 points — will spill) Velocity: 69 points (vs 63 avg last 4 cycles, ↑ 10%) Avg cycle time: 2.4 days (↓ from 3.0) Review time p50: 4h (↓ from 7h — the auto-reviewer is working) Shipped this week: - Proration support for subscription upgrades (@sam) - Dashboard v2 frontend scaffolding (@mina + @arjun) - Dependabot cleanup — zero alerts (@devi) - Intercom webhook retries (@priya-eng) Slipped: - ENG-4782: Payment webhook v3 migration — blocked 3 days on Stripe beta (@devi) - ENG-4799: Brand color decision — blocked on @alex Engineer of the cycle: @devi (100% first-time-right, 7 issues shipped) Next cycle planning on Monday 10 AM. Want me to draft the cycle 33 scope based on the triage backlog?

More Linear use cases

Deploy this in minutes

Create a LunoGen agent, connect Linear, and start running this workflow from WhatsApp today.

Back to Linear