ENGINEERING
Weekly error-budget burndown report to engineering
Each week it queries Honeycomb for every tracked SLO's remaining error budget and burn trend, writes a ranked burndown summary to Notion.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: weekly before reliability review
- ActionPull remaining budget + burn trend per SLOHoneycomb
- LogicRank services by budget-at-risk
- ActionWrite burndown report to NotionNotion
- OutputPost at-risk services + report link to SlackSlack
What it does
This gives engineering leadership a recurring, readable view of where error budget is being spent. It compiles every SLO's remaining budget and recent burn trend into a ranked report, surfacing which services are trending toward a freeze before they actually trip one.
When to use it
Use it for sprint planning or a weekly reliability review when you want a proactive budget picture instead of only reacting to alerts. Good for teams with several SLOs to keep in view at once.
How it works
- 1A schedule trigger runs weekly before the reliability review.
- 2An action pulls remaining error budget and burn trend for each tracked SLO from Honeycomb.
- 3A logic step ranks services by budget-at-risk and flags any projected to exhaust budget within the period.
- 4An action writes the formatted burndown report as a Notion page in the engineering space.
- 5The output posts the top at-risk services and a link to the full report into the team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect NotionPages, databases, comments.
- 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
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.
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.
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.
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…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.