DEVOPS
Quarterly DORA Narrative Review for Leadership
Once a quarter, an agent pulls all four DORA metrics from Snowflake, writes a plain-English performance narrative with wins and risks.
How it runs
The automated pipeline, trigger to output.
- TriggerFirst-business-day-of-quarter schedule
- ActionQuery quarter and prior-quarter DORA metricsSnowflake
- ActionAgent drafts interpreted performance narrative
- LogicValidate required narrative sections present
- OutputPublish review page to ConfluenceConfluence
What it does
This workflow produces the quarterly engineering-performance writeup that someone usually assembles by hand. An agent reads the quarter's four DORA metrics from Snowflake, compares them to the prior quarter and to DORA performance bands, and drafts a narrative that explains what moved, why it likely moved, and what the risks are. It then publishes the writeup as a Confluence page ready for the leadership review.
When to use it
Use it ahead of quarterly business reviews or board updates when you need an interpreted story, not just a chart. Best for engineering leaders who want consistent, defensible narratives without spending a day writing them.
How it works
- 1A schedule fires on the first business day of each quarter.
- 2The flow queries Snowflake for deploy frequency, lead time, change-failure rate, and time-to-restore across the quarter and the prior one.
- 3The agent reasons over the deltas, maps each metric to its DORA performance band, and drafts a structured narrative with highlights and risks.
- 4A logic step checks the draft for required sections before publishing.
- 5The final step creates a formatted Confluence page under the engineering space.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.