ENGINEERING
Escalate Zero-Evaluation Flags Past Cleanup SLA
Weekly, finds flags that have received zero evaluations in the last 14 days yet remain defined.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule starts the SLA check
- ActionQuery Postgres for zero-evaluation defined flagsPostgres
- LogicKeep only flags past the cleanup SLA window
- ActionOpen GitLab removal MR per qualifying flagGitLab
- OutputTrigger PagerDuty escalation to owning teamPagerDuty
What it does
Targets the worst class of flag debt: flags still defined in the system but evaluated zero times in the past two weeks, meaning no code path touches them. When such a flag has exceeded the cleanup SLA window, it both opens a removal MR and escalates to the owning team through PagerDuty so the debt cannot be silently ignored.
When to use it
Use this when soft reminders have not worked and flag debt keeps slipping. Zero-evaluation flags are unambiguous dead weight, so they justify firmer enforcement. The PagerDuty step is intentionally assertive: it is meant for organizations with an explicit flag-lifecycle SLA they want to hold teams to.
How it works
- 1A weekly schedule starts the check.
- 2Query Postgres evaluation metrics for flags with zero evals in 14 days that are still defined.
- 3Branch: keep only flags whose dead duration exceeds the cleanup SLA.
- 4Open a GitLab MR removing each qualifying flag and its definition.
- 5Trigger a PagerDuty incident routed to the owning team with the flag and MR link.
- 6Record the escalation so repeat offenders are visible.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.