Summarize sprint progress in Linear automatically

An Orkeste agent reads Linear daily, summarizes shipped work, in-progress tickets, blockers and at-risk scope, and posts a clean update to Slack after the engineering lead's approval.

How the workflow runs

1. Scan Linear daily: Reads ticket state changes, comments and completed work since last summary.
2. Group by epic and owner: Aggregates progress into a structured view per epic and per owner.
3. Draft narrative: Composes a digest: shipped, in-flight, blocked, at-risk.
4. Eng lead approves: Lead reviews framing, especially on blockers and risks, before posting.
5. Post to Slack: Approved summary is posted to a stakeholder channel on schedule.

Human-in-the-loop: No external stakeholder update is posted without an engineering lead's approval of the framing.

Works with your stack

• linear
• slack
• jira

Related workflows

• Detect blocked or silently stalled Linear issues
• Triage incoming bugs in Jira automatically
• Compile a weekly marketing digest in Slack

Questions about this workflow

Can it pull from both Linear and Jira?

Yes. Teams running both can produce a unified update across systems.

How does it handle confidential work?

Items tagged confidential are excluded from external summaries and only surface in internal ones.

Does it support per-team digests?

Yes. You can configure a weekly digest per squad with the right audience for each.