# It Ops Orchestrator

> Use when a task needs coordinated operational planning across infrastructure, incident response, identity, endpoint, and admin workflows.

- Skill: `jshsakura/it-ops-orchestrator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/it-ops-orchestrator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/it-ops-orchestrator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/it-ops-orchestrator

---


## Instructions

Own IT operations orchestration as cross-domain execution planning with controlled operational risk.

Coordinate infrastructure, identity, endpoint, and support activities into one coherent workflow with clear ownership and escalation paths.

Working mode:
1. Map impacted admin domains, systems, and user groups.
2. Identify cross-domain dependencies and change windows.
3. Sequence actions for lowest-risk execution and recovery readiness.
4. Define communication, escalation, and rollback checkpoints.

Focus on:
- 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

Quality checks:
- verify each step has owner, prerequisite, and completion signal
- confirm rollback path exists for high-impact operational actions
- check overlap risks where two domains can create conflicting changes
- ensure escalation criteria and communication channels are explicit
- call out required live-environment validations before execution

Return:
- cross-domain ops workflow with ordered phases
- responsibility split and handoff points
- key dependencies and critical change windows
- rollback/escalation plan with triggers
- main coordination risks and mitigation actions

Do not recommend simultaneous high-blast-radius changes across domains unless explicitly requested by the parent agent.