---
name: Memorix Orchestrate
slug: memorix-orchestrate
category: AI Engineering
description: Memorix Orchestrate coordinates explicit subagent work with tasks, handoffs, messages, file locks, and the orchestrate CLI. Use it when a main agent needs managed multi-agent execution.
github: "https://github.com/AVIDS2/memorix/tree/main/plugins/claude/memorix/skills/memorix-orchestrate"
language: TypeScript
stars: 681
forks: 53
install: "npx degit https://github.com/AVIDS2/memorix/tree/main/plugins/claude/memorix/skills/memorix-orchestrate ~/.claude/skills/memorix-orchestrate"
installs_to: ~/.claude/skills/memorix-orchestrate
source_path: plugins/claude/memorix/skills/memorix-orchestrate/SKILL.md
collection_size: 10
category_size: 2451
collection_url: "https://dirskills.com/collections/AVIDS2/memorix"
added: 2026-08-24T05:16:07.360Z
last_synced: 2026-08-24T05:16:07.360Z
canonical_url: "https://dirskills.com/skills/memorix-orchestrate"
---

# Memorix Orchestrate

Memorix Orchestrate coordinates explicit subagent work with tasks, handoffs, messages, file locks, and the orchestrate CLI. Use it when a main agent needs managed multi-agent execution.

**Install:**

```bash
npx degit https://github.com/AVIDS2/memorix/tree/main/plugins/claude/memorix/skills/memorix-orchestrate ~/.claude/skills/memorix-orchestrate
```

## README

# Memorix Orchestrate

Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.

## Tool Router

| Situation | Prefer | CLI fallback |
|---|---|---|
| Run managed subagent execution | CLI | `memorix orchestrate --goal "<goal>" --agents claude:1,codex:1` |
| Register coordination identity | `team_manage` action `join` | `memorix team join --agentType <agent>` |
| Create or inspect tasks | `team_task` | `memorix task create|list|claim|complete` |
| Send or read coordination messages | `team_message` | `memorix message send|broadcast|inbox` |
| Share structured handoff | `memorix_handoff` | `memorix handoff send` |
| Avoid file conflicts | `team_file_lock` | `memorix lock lock|unlock|status` |
| Poll joined coordination state | `memorix_poll` | `memorix poll` |

## Boundaries

- For ordinary memory, do not join coordination state.
- For production multi-agent execution, prefer `memorix orchestrate` so the main process owns planning, dispatch, retries, and verification gates.
- In worker prompts, use the worker agent ID returned by session start or team join; never use the coordinator ID as the worker identity.