AI AGENTS
Re-estimate a Linear story when its acceptance criteria change
When acceptance criteria are edited on a Linear issue, an agent re-reads the full spec and proposes an updated point estimate.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue-updated webhook firesLinear
- LogicConfirm acceptance criteria actually changed
- ActionRe-estimate points from current criteriaOpenAI
- LogicExit if estimate within one bucket
- OutputComment proposed estimate and flag for re-pointingLinear
What it does
This agent watches for edits to a Linear issue's acceptance criteria and treats every change as a trigger to re-evaluate scope. It recomputes a point estimate from the current criteria and, if the new number meaningfully differs from what is on the issue, posts a comment explaining the drift so the team can re-point before committing.
When to use it
Use it on teams where criteria get refined after initial estimation and stale point values silently corrupt sprint capacity math. It keeps estimates honest without forcing a full re-grooming meeting.
How it works
- 1A Linear webhook fires when an issue is updated.
- 2A logic step confirms the acceptance-criteria section actually changed (not just a label or assignee).
- 3The agent sends the full description plus criteria to an LLM with your team's estimation rubric.
- 4The LLM returns a point estimate and a one-line rationale.
- 5A logic step compares it to the current estimate and exits if they are within one bucket.
- 6On divergence, the agent posts a Linear comment proposing the new estimate and flags the issue for re-pointing.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.