# delivery-manager

delivery-manager — a skill for managing software delivery: plans releases, picks deployment strategies, coordinates incidents, and tracks reliability budgets. Use it to standardize how your team ships code.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 193 installs · ★ 1183 repo stars
- Author: borghei
- License: LicenseRef-MIT-Commons-Clause · policy=link-only · description only; the file stays with the author
- Source: https://github.com/borghei/Claude-Skills/tree/HEAD/project-management/delivery-manager/SKILL.md
- Updated: 2026-11-08
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/delivery-manager

## What it does

This skill acts as a delivery manager embedded in your development environment. It assesses pipeline maturity across five levels (from manual processes to DevOps Excellence), shapes release plans with clear exit criteria and Go/No-Go gates, chooses a deployment strategy (blue-green, canary, rolling, big-bang) and designs the rollback path.

Three Python scripts support the workflow. `delivery_metrics_tracker.py` reports DORA metrics over a time window. `dependency_mapper.py` visualizes cross-service and cross-team dependencies. `risk_register.py` scores delivery risks and tracks mitigations. For incidents, the skill follows a five-step cycle (detect, triage, respond, resolve, review) with four severity levels and mandatory post-mortems.

The skill enforces error-budget discipline: when the budget burns out, the team pauses features and focuses on reliability work instead. Requires Python to run the included scripts and clear exit criteria or SLA targets before generating output.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add borghei/Claude-Skills --skill delivery-manager -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/delivery-manager/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/delivery-manager/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add borghei/Claude-Skills --skill delivery-manager -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/delivery-manager/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add borghei/Claude-Skills --skill delivery-manager -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/delivery-manager/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install borghei/Claude-Skills project-management/delivery-manager/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/delivery-manager/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add borghei/Claude-Skills --skill delivery-manager -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/borghei/Claude-Skills --path project-management/delivery-manager
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/delivery-manager/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add borghei/Claude-Skills --skill delivery-manager -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/borghei/Claude-Skills/tree/HEAD/project-management/delivery-manager/SKILL.md

## When to use it
- plan a release and validate all exit criteria before shipping
- select a deployment strategy and design the rollback path
- classify an incident and coordinate the response
- calculate error-budget burn rate and decide whether to freeze features
- assess pipeline maturity and target the next level

## Example prompts
- I'm preparing a release. What exit criteria should we set and how do we run Go/No-Go?
- Pick a deployment strategy for a system that serves millions of users.
- We have a SEV-1 incident in production. What do we do in the first 15 minutes?

## Similar
- [media-qc-delivery](https://affpapa.org/en/nevibecode/skills/media-qc-delivery.md) — skill · 214 installs
- [Uptimepage](https://affpapa.org/en/nevibecode/mcp/uptimepage.md) — MCP server · ★ 61 repo stars
- [SolidPing](https://affpapa.org/en/nevibecode/mcp/solidping.md) — MCP server · ★ 46 repo stars
- [Fettle](https://affpapa.org/en/nevibecode/mcp/fettle.md) — MCP server
- [shipping-and-launch](https://affpapa.org/en/nevibecode/skills/shipping-and-launch.md) — skill · 74200 installs
- [launch-checklist](https://affpapa.org/en/nevibecode/skills/donchitos-launch-checklist.md) — skill · 683 installs

From the same set: [borghei/claude-skills](https://affpapa.org/en/nevibecode/by/borghei/claude-skills.md) — 120 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
