Playbooks / Dev Ops
Dev Ops — 11 workflows.
The technical operations layer for the owner's product or site: deploys deliberate, monitors watched, incidents handled calmly, and costs questioned. Explains technical findings in plain business language.
What ships
- 11 workflows, installed at setup.
- 4 categories, each with its own operating rules.
- Approval gates on anything client-facing or money-touching.
See it run in the live demo.
Deploys + Releases
Deploy Runbooks
Writes the per-project deploy runbook: pre-checks, steps, verification, and rollback. Any process done twice gets a runbook.
See the workflow →Release Notes from Commits
Turns commit history into human-readable notes grouped by impact: new, improved, fixed. Internal jargon translated or cut.
See the workflow →Rollback Plans
Before risky changes: the rollback path, its blast radius, and the trigger conditions. Hope is not a rollback plan.
See the workflow →Monitoring + Incidents
Health Check Setup
Defines the checks that matter: uptime, key pages, core actions, error rates. Plain-language alert routing so the right person sees the right severity.
See the workflow →Log Triage
On errors or weirdness: pull the relevant logs, separate signal from noise, and summarize the real issue with evidence. Recommend the fix path; don't apply it blind.
See the workflow →Incident Response
When something breaks: the timeline of what happened, the status updates drafted for customers at each stage (honest, no spin), and the post-incident writeup with root cause and prevention.
See the workflow →Security + Backups
Dependency + Patch Watch
Flags vulnerable or wildly outdated dependencies with plain-language risk and the upgrade path. Batch the safe updates; isolate the risky ones.
See the workflow →Access Reviews
Quarterly: who has access to what, what's unused, what violates least-privilege. Propose revocations; owner confirms.
See the workflow →Backup Verification
Backups exist only if they restore. Verifies on a schedule that the backup restores, how long it takes, and what would actually be lost.
See the workflow →Cost + Performance
Cloud Cost Review
Monthly: what we pay for, what changed, what's idle or oversized. Plain recommendations ranked by savings; owner decides changes.
See the workflow →Performance Checkups
Periodic speed and size audit of key pages and flows: what's slow, why, and the fix ranked by effort-to-impact.
See the workflow →Want this track running, not just listed?
Every workflow here is already installed in the Dev Ops agent. Walk the live box and put one of them to work.