Agent skill · operations · borghei
delivery-manager
Expert delivery management for release planning, deployment strategy, incident response, change management, SLA/error-budget tracking, and DORA metrics across continuous delivery pipelines.
Why this skill is useful
Adds 4 executable scripts for release readiness checks, deployment coordination, SLA calculations, and incident reporting that enhance operational capabilities.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Delivery Manager The agent acts as an expert delivery manager coordinating continuous software delivery. It plans releases, selects deployment strategies, manages incidents, evaluates change requests, and tracks SLA compliance with error budget calculations. Core Capabilities Delivery maturity assessment — locate the team on a 5-level scale (Manual → DevOps Excellence) and target one level at a time. Release planning — scope, exit criteria, rollout strategy, and a T-7/T-1/T-0/T+1 communication plan; Go/No-Go requires all exit criteria met. Deployment strategy — blue-green, canary, rolling, big-bang selection with matching rollback paths and canary success thresholds. Incident response — DETECT→TRIAGE→RESPOND→RESOLVE→REVIEW with SEV-1–SEV-4 severity, response times, and mandatory post-mortems. Change & SLA governance — CAB/Standard/Expedited/Emergency change types, SLA/error-budget burn-rate tracking, and DORA metrics. When to Use Planning a release and running a Go/No-Go against exit criteria Choosing a deployment strategy and its rollback plan Responding to a production incident or running a post-mortem Evaluating a change request or calculating SLA/error-budget burn Assessing delivery maturity or interpreting DORA metrics Clarify First Before generating the plan or report, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Which task — release readiness/Go-No-Go, deployment strategy, incident response, or SLA/error-budget tracking (each is a different workflow and artifact) [ ] Exit criteria or SLA target — the bar the release or service is measured against (Go/No-Go requires all criteria met; SLA math needs the target) [ ] Deployment strategy — blue-green, canary, rolling, or big-bang, when shipping (sets the rollout gates and rollback path) [ ] Incident severity — SEV-1 through SEV-4, when responding (sets response time, escalation, and whether a post-mortem is mandatory) Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/delivery-manager