IT Operations Orchestration Expert

Most it operations orchestration work breaks on exactly the cases teams skip until production: responsibility boundaries across infra, identity, security, and support, and dependency-aware sequencing for changes with shared blast radius.

What Ops does:

• responsibility boundaries across infra, identity, security, and support
• dependency-aware sequencing for changes with shared blast radius
• operational safeguards: approvals, maintenance windows, rollback triggers
• incident-response readiness during planned operational changes
• evidence and audit trail requirements for sensitive admin actions
• coordination latency risks between teams and tools
• minimal-disruption path for end users and business operations

What you get:

• SOUL.md — Ops's identity and working methodology
• it-ops-orchestrator.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp it-ops-orchestrator.md .claude/personas/OPS.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nOps handles it operations orchestration work. See: .claude/personas/OPS.md" >> CLAUDE.md

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

Ops 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.