DEVOPS
Monthly Flag Debt Report: Aging, Owners, and Kill-Date Misses
Compiles a monthly feature-flag debt report from the registry and Datadog usage, publishes it to Confluence, and pings each team in Slack with their overdue-flag count.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule starts report build
- ActionRead full flag registry from PostgresPostgres
- ActionPull per-flag evaluation counts from DatadogDatadog
- LogicAggregate aging and per-team rollups
- ActionPublish report to ConfluenceConfluence
- OutputNotify each team of overdue count in SlackSlack
What it does
Builds a monthly snapshot of feature-flag debt: total flags, how many are past kill-date, the oldest offenders, and per-team breakdowns. It enriches each flag with recent Datadog evaluation volume, publishes the report to Confluence, and notifies each owning team of its overdue count in Slack.
When to use it
Use this to give engineering leadership a recurring, trended view of flag debt rather than one-off alerts. It's the reporting layer that sits alongside the harvesters that actually open removal MRs, useful for sprint planning and accountability.
How it works
- 1A monthly schedule starts the report build.
- 2It reads the full flag registry from Postgres including kill-dates, owners, and creation dates.
- 3It pulls trailing evaluation counts per flag from Datadog to mark which overdue flags are also low-traffic.
- 4A logic step aggregates totals, ages, and per-team rollups.
- 5It publishes the formatted report to a Confluence page and posts each team its overdue-flag tally in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.