EvolutionAPI

Helm Conductor — DevOps skill for Claude Code

DevOps community

Use the @helm-conductor agent to orchestrate the engineering cycle — sequence features, decide what to work on next, route tasks to the right specialist agent, or plan a sprint: $ARGUMENTS.

How to install Helm Conductor

Installs to ~/.claude/commands/evolutionapi-evo-nexus-helm-conductor.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/EvolutionAPI/evo-nexus/HEAD/.claude/commands/helm-conductor.md -o ~/.claude/commands/evolutionapi-evo-nexus-helm-conductor.md

Restart Claude Code, or start a new session, for it to be picked up.

What Helm Conductor does

Use the @helm-conductor agent to orchestrate the engineering cycle — sequence features, decide what to work on next, route tasks to the right specialist agent, or plan a sprint: $ARGUMENTS

Helm is the conductor, not a worker. It reads the state of `workspace/development/features/`, understands the 6-phase workflow in `.claude/rules/dev-phases.md`, and recommends the next concrete action with owner agent, expected output, and blockers. If no arguments are provided, Helm should read the feature f

Alternatives in DevOps

Claude Code Router — Use Claude Code as the foundation for coding infrastructure, allowing you to decide how to interact with the m 30.1k ★
Vinext — Vite plugin that reimplements the Next.js API surface — deploy anywhere 8.7k ★
Proxy — route Claude Code requests through multiple upstream providers (OpenCode Go, OpenCode Zen, and AWS Bedrock) wi 957 ★