ENGINEERING
Flag runbooks stale since the service last deployed
On a weekly schedule, compares each service's last GitHub release date against the last-edited date of its Confluence runbook.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the audit
- ActionFetch latest release date per repo from GitHubGitHub
- ActionRead runbook last-modified date from ConfluenceConfluence
- LogicKeep runbooks older than their service's last deploy
- LogicRank stale runbooks by staleness window
- OutputPost ranked staleness digest to SlackSlack
What it does
Surfaces on-call runbooks that have drifted behind the code they document. For each service, it reads the latest GitHub release timestamp and the matching Confluence runbook's last-modified date, then flags any runbook older than its newest deploy so owners know exactly what needs a refresh.
When to use it
Run it weekly when your runbooks live in Confluence and you ship through tagged GitHub releases. It is the lightweight first line of defense against the classic incident-night surprise of a runbook describing infrastructure that changed three deploys ago.
How it works
- 1A weekly schedule fires the audit.
- 2It pulls the latest release per repo from GitHub, capturing the published-at date.
- 3It fetches each service's runbook page from Confluence and reads its last-updated timestamp.
- 4A comparison step keeps only services whose runbook date is earlier than the release date.
- 5Stale entries are formatted into a ranked digest (oldest gap first).
- 6The digest is posted to a Slack channel, tagging each runbook owner with the staleness window in days.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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.