From dispatch
Dispatch a task to external agent CLIs through the dispatch external-agent router — compose a self-contained task brief, probe all agent facts in one matrix call, and receive the outputs verbatim as evidence. The audit and image-generation skills build on this one; use it directly only when the user directs an external-agent task outside those types.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dispatch:use-external-agentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Announce at start:** "Dispatching through the dispatch external-agent router."
Announce at start: "Dispatching through the dispatch external-agent router."
Resolve ATTUNE_ROOT to the absolute path two directories above this skill's directory — your harness names that directory when it loads this skill — before running any command quoted below. ATTUNE_ROOT is the installed plugin root; the agent registry lives at $ATTUNE_ROOT/capabilities.json.
One path delegates work to an external agent: the dispatch:external-agent router subagent. Launch it with your subagent tool (on Claude Code, the Agent tool with subagent_type: "dispatch:external-agent"), passing the whole task brief as its prompt — one launch per brief. The router verifies CLI parameters against each agent's current --help, launches headless runs, and responds as the brief's Response section specifies.
MUST:
AGENTS line — the router dispatches to exactly those and never chooses on its own.MUST NOT:
## Metadata
- GOAL: <one line — what the task must accomplish>
- TAGS: <task traits, e.g. auditing, image-generation>
- AGENTS: <the agents to dispatch to — the dispatching skill pins them>
- CAPABILITIES_MARKER: <optional path to an existing fact marker; omit to let the router probe once itself>
## External Agent Task Prompt
<EXTERNAL_AGENT_TASK_PROMPT>
<the full, self-contained task prompt for the external agent — it sees nothing else>
</EXTERNAL_AGENT_TASK_PROMPT>
## Response
<how the router responds to the main conversation — the report shape, including artifact paths when the task produces artifacts>
One command answers everything in one call, printing installed / usable / capable per registry agent:
bash "$ATTUNE_ROOT/scripts/external-agents.sh" matrix <marker.json>
<marker.json> is any writable path you pick: the first call probes and writes its memo there; later calls re-render from it free.
MUST:
CAPABILITIES_MARKER so the router never re-probes.MUST NOT:
MUST:
bash "$ATTUNE_ROOT/scripts/worktree.sh" create <repo-dir> <name> prints the worktree path — point the external agent at that path as its working directory, collect the changes with worktree.sh diff <worktree-path> as evidence, merge or discard explicitly in the main conversation, then worktree.sh remove <repo-dir> <worktree-path>.MUST NOT:
MUST:
$ATTUNE_ROOT/capabilities.json) verified against fresh --help output — external CLIs update frequently.MUST NOT:
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub wezzard/skills --plugin dispatch