PERSONAL PRODUCTIVITY
Draft KR Updates When a Linear Cycle Closes
When a Linear cycle completes, it maps the cycle's finished issues to their key results and posts a drafted KR progress update into the OKR tracking channel for the owner…
How it runs
The automated pipeline, trigger to output.
- TriggerLinear cycle completesLinear
- ActionFetch issues closed in the cycle with labelsLinear
- LogicGroup closed issues by KR label, drop unlabeled
- ActionDraft per-KR progress update citing shipped workOpenAI
- OutputPost drafts to OKR channel, tag KR ownersSlack
What it does
It ties engineering delivery directly to OKR reporting. When a Linear cycle ends, the workflow gathers the issues completed in that cycle, attributes them to the key results they advanced via issue labels, and drafts a per-KR progress update so the KR owner can confirm movement the moment a sprint wraps.
When to use it
Use it for product and engineering teams whose key results are delivered through Linear cycles. It is best when you want OKR updates to land on cycle boundaries instead of an arbitrary calendar day.
How it works
- 1A Linear cycle-completed event triggers the run.
- 2It fetches all issues closed in that cycle along with their labels and estimates.
- 3A logic step groups completed issues by the KR label they carry and drops any issue without an OKR label.
- 4An OpenAI step drafts a short progress update per affected KR, citing the shipped issues.
- 5It posts each draft to the OKR channel in Slack, tagging the KR owner to confirm or revise.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Personal Productivity workflows
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Email-to-Task: Turn Action-Required Mail Into Linear Issues
Detects mail that contains a concrete task or request, extracts the deliverable and due date, and creates a Linear issue automatically so commitments from email never get lost.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.