菜单
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
| name | memorix-orchestrate |
| description | Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI. |
Use Memorix coordination for explicit subagent workflows with joined identities, tasks, handoffs, messages, file locks, and orchestrated workers.
| 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 |
| Send or read coordination messages | team_message | `memorix message send |
| Share structured handoff | memorix_handoff | memorix handoff send |
| Avoid file conflicts | team_file_lock | `memorix lock lock |
| Poll joined coordination state | memorix_poll | memorix poll |
memorix orchestrate so the main process owns planning, dispatch, retries, and verification gates.