ENGINEERING
Weekly Stale-Flag Digest to Slack
Compiles all feature flags that are fully rolled out and overdue for removal into a single ranked Slack digest.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers digest
- ActionQuery Postgres for stale 100% flagsPostgres
- ActionCount refs and resolve owning teamGitHub
- LogicRank flags by staleness and blast radius
- OutputPost ranked digest to Slack with team mentionsSlack
What it does
Gives the team a low-friction weekly view of which flags should be removed, ranked by how long they've been stale and how many call sites they touch. Nothing is changed in the repo; it's a visibility report that prompts owners to act.
When to use it
Use it when you want awareness before automation, or when your codebase's flag patterns are too varied for safe auto-rewrites. A good first step toward a cleanup culture.
How it works
- 1A weekly schedule triggers the digest.
- 2Query Postgres for every flag at 100% rollout past the staleness threshold.
- 3For each, count references and find the owning team via GitHub blame and CODEOWNERS.
- 4A logic step ranks flags by staleness age times call-site count.
- 5Format a digest grouping flags by owning team with age and reference counts.
- 6Post the ranked digest to the engineering Slack channel with @-mentions per team.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.