DEVOPS
Quarterly Feature-Flag Debt Audit with Owner Triage
An agent reviews the entire flag inventory against telemetry each quarter, classifies every flag (keep, remove, investigate), and publishes a Confluence report…
How it runs
The automated pipeline, trigger to output.
- TriggerQuarterly schedule fires
- ActionPull full flag inventory and telemetry from AxiomAxiom
- ActionGather call sites and history from GitHubGitHub
- LogicAgent classifies each flag keep/remove/investigate
- ActionPublish Confluence audit page by owning teamConfluence
- OutputOpen owner-assigned Linear issues for removable flagsLinear
What it does
Runs a full portfolio audit of every feature flag in the system. An agent pulls usage telemetry, reads each flag's call sites, and reasons about whether it's a permanent config, a finished rollout, an abandoned experiment, or genuinely still in flight — then produces a human-readable audit and actionable cleanup tasks.
When to use it
For a recurring governance review where someone needs a defensible, owner-by-owner picture of flag health, not just a flat list. The agent's per-flag reasoning handles ambiguous cases a threshold rule would mislabel.
How it works
- 1A quarterly schedule starts the audit.
- 2Pull the complete flag inventory and per-flag evaluation telemetry from Axiom.
- 3For each flag, gather call sites and history from GitHub.
- 4The agent classifies every flag as keep, remove, or investigate with a written rationale.
- 5Publish a Confluence audit page grouped by owning team with the full classification.
- 6Open Linear issues for each remove/investigate flag, assigned to its owner.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.