Back to Details

using-orchestration

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Using the Orchestration System

编排系统使用指南

When to Suggest

建议使用场景

Proactively suggest 
/orchestrate
when user describes:
Clear Triggers:
  • Multiple agents needed in sequence: "explore then review then implement"
  • Parallel operations: "run tests and lint at the same time"
  • Conditional workflows: "if tests pass, deploy; if failed, fix and retry"
  • Retry logic: "keep trying until it works"
  • Workflow automation: "I do this same process often"
  • Multiple checkpoints: "I want to review before deploying"
Specific Phrases:
  • "coordinate multiple agents"
  • "workflow", "pipeline", "orchestrate"
  • "run these in parallel"
  • "if X then Y"
  • "retry until success"
  • "automate this process"
当用户描述以下场景时，主动建议使用
/orchestrate
：
明确触发场景：
  • 需要多个Agent串行执行：“先探索、再评审、最后实现”
  • 并行操作：“同时运行测试与代码检查”
  • 条件式工作流：“如果测试通过则部署；如果失败则修复并重试”
  • 重试逻辑：“持续尝试直到成功”
  • 工作流自动化：“我经常执行这个相同的流程”
  • 多检查点：“我想在部署前进行评审”
特定表述：
  • “协调多个Agent”
  • “工作流”、“流水线”、“编排”
  • “并行运行这些任务”
  • “如果X则执行Y”
  • “重试直到成功”
  • “自动化这个流程”

How to Introduce

介绍方式

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.
检测到触发场景时，主动建议：
这个工作流可通过编排来优化。我可以使用`/orchestrate`来：
- 可视化工作流图
- 在可行的情况下并行执行Agent
- 处理重试与条件逻辑
- 在检查点提供交互式控制

您希望我使用`/orchestrate [workflow-syntax]`还是创建一个可复用的模板？
首次设置提醒：
如果用户提及的自定义Agent（如
expert-code-implementer
、
code-optimizer
等）不在编排命名空间中：
我注意到您的环境中有自定义Agent。
是否需要先将它们导入到编排系统中？

执行命令：/orchestration:init

执行后，您的自定义Agent将可在工作流中使用，格式如下：
- orchestration:expert-code-implementer
- orchestration:code-optimizer
- 等等

Quick Syntax Reference

快速语法参考

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
根据用户需求展示相关语法：
串行执行： 
explore:"task" -> review -> implement
并行执行： 
[test || lint || security]
条件执行： 
test (if passed)~> deploy
重试逻辑： 
@try -> fix -> test (if failed)~> @try

When NOT to Suggest

不建议使用场景

  • Single agent task (no coordination needed)
  • Simple sequential tasks (<3 steps, no conditionals)
  • User explicitly requests manual coordination
  • Task already in progress without orchestration
  • 单Agent任务（无需协调）
  • 简单串行任务（少于3个步骤，无条件逻辑）
  • 用户明确要求手动协调
  • 未使用编排系统的任务已在执行中

Integration Pattern

集成流程

When user agrees to orchestration:
  1. Parse their requirements into workflow syntax
  2. Invoke 
    /orchestrate [workflow-syntax]
  3. Let the orchestration system handle execution
  4. Don't manually coordinate agents - let orchestrator do it
当用户同意使用编排系统时：
  1. 将用户需求转换为工作流语法
  2. 调用
    /orchestrate [workflow-syntax]
  3. 由编排系统处理执行过程
  4. 不要手动协调Agent，交由编排系统处理