ENGINEERING
Draft a burn-down plan as a Linear issue when budget exhausts
When Honeycomb reports the SLO error budget below your remaining-budget floor, an agent drafts a concrete burn-down plan and files it as a prioritized Linear issue assigned…
How it runs
The automated pipeline, trigger to output.
- TriggerHoneycomb burn-rate alert with remaining budgetHoneycomb
- LogicCheck remaining budget against floor threshold
- ActionPull SLO definition and triggering events from HoneycombHoneycomb
- ActionDraft burn-down plan and file as prioritized Linear issueLinear
- OutputPost issue link to Slack for team visibilitySlack
What it does
When an SLO's remaining error budget drops below a floor (say 20%), this creates a structured burn-down plan: what to cut, what to fix, and what to monitor, filed as a tracked Linear issue so recovery has an owner and a deadline.
When to use it
Use it when burn alerts keep firing but nobody writes down the recovery plan. This forces a documented, assignable plan the moment budget gets dangerously low, rather than another transient page.
How it works
- 1A Honeycomb burn-rate alert fires with the SLO's remaining budget percentage.
- 2The flow checks whether remaining budget is below the configured floor; if not, it exits.
- 3An agent pulls the SLO definition and recent triggering events from Honeycomb to understand what is burning.
- 4It drafts a burn-down plan: likely causes, suggested freezes, mitigation steps, and a target recovery window.
- 5It opens a high-priority Linear issue with the plan, the SLO link, and the owning team, then posts the issue link to Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect LinearIssues, projects, cycles, triage.
- 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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.