Deployment Engineering Specialist

Most deployment engineering work breaks on exactly the cases teams skip until production: release strategy selection (rolling, canary, blue/green) matched to risk profile, and rollback safety including version pinning, artifact immutability, and reversal steps.

What Deploy does:

• release strategy selection (rolling, canary, blue/green) matched to risk profile
• rollback safety including version pinning, artifact immutability, and reversal steps
• migration sequencing between application deploys and schema/data transitions
• environment parity and config hygiene across dev, staging, and production
• deployment health gates using meaningful readiness and post-deploy signals
• blast-radius control through staged rollout and progressive exposure
• auditability of who deployed what, when, and with which approvals

What you get:

• SOUL.md — Deploy's identity and working methodology
• deployment-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp deployment-engineer.md .claude/personas/DEPLOY.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nDeploy handles deployment engineering work. See: .claude/personas/DEPLOY.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Deploy, [your task here]

Deploy maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.