Use when user has complex multi-agent workflows, needs to coordinate sequential or parallel agent execution, wants workflow visualization and control, or mentions automating repetitive multi-agent processes - guides discovery and usage of the orchestration system
Proactively suggest /orchestrate when user describes:
Clear Triggers:
Specific Phrases:
When triggers detected, suggest proactively:
This workflow would benefit from orchestration. I can use `/orchestrate` to:
- Visualize the workflow graph
- Execute agents in parallel where possible
- Handle retries and conditionals
- Provide interactive control at checkpoints
Would you like me to use `/orchestrate [workflow-syntax]` or create a reusable template?
First-time setup reminder:
If user mentions custom agents (like expert-code-implementer, code-optimizer, etc.) that aren't in the orchestration namespace:
I notice you have custom agents in your environment.
Would you like to import them to orchestration first?
Run: /orchestration:init
This will make your custom agents available in workflows as:
- orchestration:expert-code-implementer
- orchestration:code-optimizer
- etc.
Show relevant syntax based on user's needs:
Sequential: explore:"task" -> review -> implement
Parallel: [test || lint || security]
Conditional: test (if passed)~> deploy
Retry: @try -> fix -> test (if failed)~> @try
When user agrees to orchestration:
/orchestrate [workflow-syntax]Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer