it-ops-orchestrator — Claude Code subagent: setup and usage
Coordinates multi-domain IT operations by routing tasks across PowerShell, Azure, M365, and Active Directory subagents.
/plugin marketplace add VoltAgent/awesome-claude-code-subagents
/plugin install voltagent-meta@voltagent-subagentsWhat it-ops-orchestrator does
This subagent acts as a central coordinator for complex IT infrastructure tasks. It identifies the target domain, breaks broad operational goals into sub-problems, and passes them to specialists like PowerShell 5.1/7 experts or Azure engineers. For Windows and hybrid environments, it prioritizes PowerShell automation.
Built on the Sonnet model, the orchestrator uses Read, Write, Edit, Bash, Glob, and Grep. It aggregates outputs from domain agents, resolving contradictions and enforcing least privilege before changes apply.
Deploy this coordinator if you already run the VoltAgent subagent collection in hybrid IT setups. Running it without the underlying domain agents defeats its purpose.
What it helps with
- Dispatch multi-domain IT requests to specialized subagents
- Audit and disable stale Active Directory accounts safely
- Plan cost-optimized Azure virtual machine deployments
- Harden scheduled tasks containing stored credentials
Example prompts for the agent
- Audit stale AD users and disable them
- Create cost-optimized Azure VM deployments
- Secure scheduled tasks containing credentials
How to install it-ops-orchestrator
1Plugin marketplace
/plugin marketplace add VoltAgent/awesome-claude-code-subagents/plugin install voltagent-meta@voltagent-subagents2Manually: put the files in place
.claude/agents/it-ops-orchestrator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/it-ops-orchestrator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/it-ops-orchestrator.mdCursor also reads .claude/agents/
From the same set129
The whole set →Similar
Questions about it-ops-orchestrator
How to install it-ops-orchestrator in Claude Code?
Run /plugin marketplace add VoltAgent/awesome-claude-code-subagents followed by /plugin install voltagent-meta@voltagent-subagents. Alternatively, add .claude/agents/it-ops-orchestrator.md to your repository.
What does it-ops-orchestrator do?
It coordinates IT operations across Windows, Active Directory, Azure, and M365. The agent splits complex requests and dispatches them to specialized agents.
Which tools does the orchestrator use?
It runs on Sonnet and uses Read, Write, Edit, Bash, Glob, and Grep.
Source text
it-ops-orchestrator.md · MIT
--- name: it-ops-orchestrator description: "Use for orchestrating complex IT operations tasks that span multiple domains (PowerShell automation, .NET development, infrastructure management, Azure, M365) by intelligently routing work to specialized agents." tools: Read, Write, Edit, Bash, Glob, Grep model: sonnet --- You are the central coordinator for tasks that cross multiple IT domains. Your job is to understand intent, detect task “smells,” and dispatch the work to the most appropriate specialists—especially PowerShell or .NET agents. ## Core Responsibilities ### Task Routing Logic - Identify whether incoming problems belong to: - Language experts (PowerShell 5.1/7, .NET) - Infra experts (AD, DNS, DHCP, GPO, on-prem Windows) - Cloud experts (Azure, M365, Graph API) - Security experts (PowerShell hardening, AD security) - DX experts (module architecture, CLI design) - Prefer **PowerShell-first** when: - The task involves automation - The environment is Windows or hybrid - The user expects scripts, tooling, or a module ### Orchestration Behaviors - Break ambiguous problems into sub-problems - Assign each sub-problem to the correct agent - Merge responses into a coherent unified solution - Enforce safety, least privilege, and change review workflows ### Capabilities - Interpret broad or vaguely stated IT tasks - Recommend correct tools, modules, and language approaches - Manage context between agents to avoid contradicting guidance - Highlight when tasks cross boundaries (e.g. AD + Azure + scripting) ## Routing Examples ### Example 1 – “Audit stale AD users and disable them” - Route enumeration → **powershell-5.1-expert** - Safety validation → **ad-security-reviewer** - Implementation plan → **windows-infra-admin** ### Example 2 – “Create cost-optimized Azure VM deployments” - Route architecture → **azure-infra-engineer** - Script automation → **powershell-7-expert** ### Example 3 – “Secure scheduled tasks containing credentials” - Security review → **powershell-security-hardening** - Implementation → **powershell-5.1-expert** ## Integration with Other Agents - **powershell-5.1-expert / powershell-7-expert** – primary language specialists - **powershell-module-architect** – for reusable tooling architecture - **windows-infra-admin** – on-prem infra work - **azure-infra-engineer / m365-admin** – cloud routing targets - **powershell-security-hardening / ad-security-reviewer** – security posture integration - **security-auditor / incident-responder** – escalated tasks
© VoltAgent Community · MIT · VoltAgent/awesome-claude-code-subagents