Official orchestrators
Valdr’s official orchestrators are the agents you use when work needs structure instead of another ad-hoc chat. Each one owns a different control-plane job: Gunnar helps you understand and create PM work, Mimir keeps workspace knowledge searchable and useful, Nikol helps you design the agent system itself, Skadi coordinates sprint execution, and Verdandi authors and operates durable workflows.
This section covers orchestrators distributed across the official Valdr packs. Availability depends on your subscription and installed packs; together they provide the command layer users reach for when they want predictable agent operations.
Note
Local control plane: Agent definitions, prompts, capabilities, tasks, reviews, sessions, and history live in your local workspace. Configured model providers receive the prompts and context sent when an agent runs.
Choose the right orchestrator
| Orchestrator | Handle | Use when you need to |
|---|---|---|
| Gunnar | gunnar | Navigate projects, tasks, sprints, agents, prompts, capabilities, and create structured tasks |
| Mimir | mimir | Curate knowledge sources, refresh indexes, search docs/code, map symbols, and capture agent memory |
| Nikol | nikol | Design agents, author capabilities, assemble manifests, and maintain Valdr packs |
| Skadi | skadi | Prepare sprints, assign executors, route reviews, launch sessions, and keep delivery moving |
| Verdandi | verdandi | Author and test workflow definitions, run and inspect workflows, diagnose stopped runs, and apply recovery |
How they work
The orchestrators stay lean at launch. Each starts with a focused system capability, then hot-loads deeper workflow guidance only when the request needs it. That keeps everyday navigation fast while still giving complex operations the detailed instructions they need.
Use them from the Orchestrator UI when you want a conversational command center, or launch them through your configured presets when another agent needs to delegate a workflow. Start with the smallest direct request that describes the outcome:
- Gunnar, show me active tasks for this project and flag anything blocked.
- Mimir, find the source of truth for our release workflow and show the relevant code symbols.
- Nikol, help me design a docs reviewer agent for our pack.
- Skadi, prepare the next sprint from these tasks and check launch readiness.
- Verdandi, inspect this blocked workflow run and explain the cause with evidence.
Good orchestrator use is explicit. Ask for the state you want inspected, the workflow you want prepared, or the handoff you want coordinated. The agent fetches current context first, then uses Valdr’s MCP tools and local PM state to make the next move inspectable.
Use an orchestrator from the CLI
The valdr-orchestrator wrapper gives Claude Code and Codex CLI one entry point for the registered orchestrators. Name a handle directly, or let the wrapper list the available choices:
/valdr-orchestrator
Use verdandi to inspect this blocked workflow run and explain the cause with evidence.The wrapper validates the selected handle, loads its current prompt, and follows the capabilities shipped by the installed pack. You can use the same orchestrators from the Orchestrator UI or launch them directly with a configured preset.
Orchestrator docs
Start with Gunnar when you are unsure where work lives, Mimir when the answer depends on searchable workspace knowledge, Nikol when the agent system itself needs maintenance, Skadi when execution needs coordination across tasks, reviewers, and sessions, and Verdandi when a durable workflow needs to be created, run, or repaired.
Need the specialists that own planning, review, and audit gates? Read Built-in specialist agents for Freya, Sigrid, and Tyr.