Skip to content
Development
Command

/orchestrate

Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly.

From plugin
ecc
239k109 skills72 agents109 commands7 hooks
+1
Install
> /plugin marketplace add affaan-m/ECC
> /plugin install ecc@ecc

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/orchestrate

Context preview

What this command does when you run it.

Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly.

Command definition

orchestrate.md
description: Legacy slash-entry shim for dmux-workflows and autonomous-agent-harness. Prefer the skills directly.

Orchestrate Command (Legacy Shim)

Use this only if you still invoke `/orchestrate`. The maintained orchestration guidance lives in `skills/dmux-workflows/SKILL.md` and `skills/autonomous-agent-harness/SKILL.md`.

Canonical Surface

  • Prefer `dmux-workflows` for parallel panes, worktrees, and multi-agent splits.
  • Prefer `autonomous-agent-harness` for longer-running loops, governance, scheduling, and control-plane style execution.
  • Keep this file only as a compatibility entry point.

Arguments

`$ARGUMENTS`

Delegation

Apply the orchestration skills instead of maintaining a second workflow spec here.

  • Start with `dmux-workflows` for split/parallel execution.
  • Pull in `autonomous-agent-harness` when the user is really asking for persistent loops, governance, or operator-layer behavior.
  • Keep handoffs structured, but let the skills define the maintained sequencing rules.
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin