ultrawork

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<Purpose> Ultrawork is a parallel execution engine that runs multiple agents simultaneously for independent tasks. It is a component, not a standalone persistence mode -- it provides parallelism and smart model routing but not persistence, verification loops, or state management. </Purpose>
<Use_When>
  • Multiple independent tasks can run simultaneously
  • User says "ulw", "ultrawork", or wants parallel execution
  • You need to delegate work to multiple agents at once
  • Task benefits from concurrent execution but the user will manage completion themselves </Use_When>
<Do_Not_Use_When>
  • Task requires guaranteed completion with verification -- use
    ralph
    instead (ralph includes ultrawork)
  • Task requires a full autonomous pipeline -- use
    autopilot
    instead (autopilot includes ralph which includes ultrawork)
  • There is only one sequential task with no parallelism opportunity -- delegate directly to an executor agent
  • User needs session persistence for resume -- use
    ralph
    which adds persistence on top of ultrawork </Do_Not_Use_When>
<Why_This_Exists> Sequential task execution wastes time when tasks are independent. Ultrawork enables firing multiple agents simultaneously and routing each to the right model tier, reducing total execution time while controlling token costs. It is designed as a composable component that ralph and autopilot layer on top of. </Why_This_Exists>
<Execution_Policy>
  • Fire all independent agent calls simultaneously -- never serialize independent work
  • Always pass the
    model
    parameter explicitly when delegating
  • Read
    docs/shared/agent-tiers.md
    before first delegation for agent selection guidance
  • Use
    run_in_background: true
    for operations over ~30 seconds (installs, builds, tests)
  • Run quick commands (git status, file reads, simple checks) in the foreground </Execution_Policy>
<Steps> 1. **Read agent reference**: Load `docs/shared/agent-tiers.md` for tier selection 2. **Classify tasks by independence**: Identify which tasks can run in parallel vs which have dependencies 3. **Route to correct tiers**: - Simple lookups/definitions: LOW tier (Haiku) - Standard implementation: MEDIUM tier (Sonnet) - Complex analysis/refactoring: HIGH tier (Opus) 4. **Fire independent tasks simultaneously**: Launch all parallel-safe tasks at once 5. **Run dependent tasks sequentially**: Wait for prerequisites before launching dependent work 6. **Background long operations**: Builds, installs, and test suites use `run_in_background: true` 7. **Verify when all tasks complete** (lightweight): - Build/typecheck passes - Affected tests pass - No new errors introduced </Steps>
<Tool_Usage>
  • Use
    Task(subagent_type="oh-my-claudecode:executor-low", model="haiku", ...)
    for simple changes
  • Use
    Task(subagent_type="oh-my-claudecode:executor", model="sonnet", ...)
    for standard work
  • Use
    Task(subagent_type="oh-my-claudecode:executor-high", model="opus", ...)
    for complex work
  • Use
    run_in_background: true
    for package installs, builds, and test suites
  • Use foreground execution for quick status checks and file operations </Tool_Usage>
<Examples> <Good> Three independent tasks fired simultaneously: ``` Task(subagent_type="oh-my-claudecode:executor-low", model="haiku", prompt="Add missing type export for Config interface") Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="Implement the /api/users endpoint with validation") Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="Add integration tests for the auth middleware") ``` Why good: Independent tasks at appropriate tiers, all fired at once. </Good> <Good> Correct use of background execution: ``` Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="npm install && npm run build", run_in_background=true) Task(subagent_type="oh-my-claudecode:executor-low", model="haiku", prompt="Update the README with new API endpoints") ``` Why good: Long build runs in background while short task runs in foreground. </Good> <Bad> Sequential execution of independent work: ``` result1 = Task(executor-low, "Add type export") # wait... result2 = Task(executor, "Implement endpoint") # wait... result3 = Task(executor, "Add tests") # wait... ``` Why bad: These tasks are independent. Running them sequentially wastes time. </Bad> <Bad> Wrong tier selection: ``` Task(subagent_type="oh-my-claudecode:executor-high", model="opus", prompt="Add a missing semicolon") ``` Why bad: Opus is expensive overkill for a trivial fix. Use executor-low with Haiku instead. </Bad> </Examples>
<Escalation_And_Stop_Conditions>
  • When ultrawork is invoked directly (not via ralph), apply lightweight verification only -- build passes, tests pass, no new errors
  • For full persistence and comprehensive architect verification, recommend switching to
    ralph
    mode
  • If a task fails repeatedly across retries, report the issue rather than retrying indefinitely
  • Escalate to the user when tasks have unclear dependencies or conflicting requirements </Escalation_And_Stop_Conditions>
<Final_Checklist>
  • All parallel tasks completed
  • Build/typecheck passes
  • Affected tests pass
  • No new errors introduced </Final_Checklist>
<Advanced>
<目的> Ultrawork是一款并行执行引擎,可同时运行多个Agent来处理独立任务。它是一个组件,而非独立的持久化模式——它提供并行处理和智能模型路由功能,但不包含持久化、验证循环或状态管理。 </目的>
<适用场景>
  • 存在多个可同时运行的独立任务
  • 用户提及“ulw”、“ultrawork”,或需要并行执行
  • 需要一次性将工作委派给多个Agent
  • 任务可从并发执行中获益,且用户将自行管理任务完成情况 </适用场景>
<不适用场景>
  • 任务需要带验证的可靠完成——请改用
    ralph
    (ralph包含ultrawork)
  • 任务需要完整的自主流水线——请改用
    autopilot
    (autopilot包含ralph,而ralph包含ultrawork)
  • 仅存在单个无并行机会的顺序任务——直接委派给执行器Agent
  • 用户需要会话持久化以恢复任务——请改用
    ralph
    ,它在ultrawork基础上增加了持久化功能 </不适用场景>
<设计初衷> 当任务相互独立时,顺序执行会浪费时间。Ultrawork支持同时启动多个Agent,并将每个任务路由到合适的模型层级,在控制Token成本的同时缩短总执行时间。它被设计为一个可组合的组件,ralph和autopilot都基于它进行了功能扩展。 </设计初衷>
<执行策略>
  • 同时启动所有独立Agent调用——绝不要序列化独立工作
  • 委派任务时始终显式传递
    model
    参数
  • 首次委派前阅读
    docs/shared/agent-tiers.md
    获取Agent选择指南
  • 对于耗时约30秒以上的操作(安装、构建、测试),使用
    run_in_background: true
  • 快速命令(git status、文件读取、简单检查)在前台运行 </执行策略>
<执行步骤>
  1. 查阅Agent参考文档:加载
    docs/shared/agent-tiers.md
    进行层级选择
  2. 按独立性分类任务:识别哪些任务可并行运行,哪些存在依赖关系
  3. 路由到正确层级:
    • 简单查询/定义:LOW层级(Haiku)
    • 标准实现:MEDIUM层级(Sonnet)
    • 复杂分析/重构:HIGH层级(Opus)
  4. 同时启动独立任务:一次性启动所有支持并行的任务
  5. 顺序运行依赖任务:在启动依赖任务前等待前置任务完成
  6. 后台运行长时操作:构建、安装和测试套件使用
    run_in_background: true
  7. 轻量级验证所有任务完成情况:
    • 构建/类型检查通过
    • 受影响的测试通过
    • 未引入新错误 </执行步骤>
<工具使用>
  • 对于简单修改,使用
    Task(subagent_type="oh-my-claudecode:executor-low", model="haiku", ...)
  • 对于标准工作,使用
    Task(subagent_type="oh-my-claudecode:executor", model="sonnet", ...)
  • 对于复杂工作,使用
    Task(subagent_type="oh-my-claudecode:executor-high", model="opus", ...)
  • 对于包安装、构建和测试套件,使用
    run_in_background: true
  • 快速状态检查和文件操作在前台执行 </工具使用>
<示例> <正确示例> 三个独立任务同时启动:
Task(subagent_type="oh-my-claudecode:executor-low", model="haiku", prompt="Add missing type export for Config interface")
Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="Implement the /api/users endpoint with validation")
Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="Add integration tests for the auth middleware")
为何正确:独立任务分配到了合适的层级,且全部同时启动。 </正确示例>
<正确示例> 后台执行的正确用法:
Task(subagent_type="oh-my-claudecode:executor", model="sonnet", prompt="npm install && npm run build", run_in_background=true)
Task(subagent_type="oh-my-claudecode:executor-low", model="haiku", prompt="Update the README with new API endpoints")
为何正确:长时间的构建在后台运行,同时短任务在前台执行。 </正确示例>
<错误示例> 独立任务顺序执行:
result1 = Task(executor-low, "Add type export")  # 等待...
result2 = Task(executor, "Implement endpoint")     # 等待...
result3 = Task(executor, "Add tests")              # 等待...
为何错误:这些任务相互独立,顺序执行会浪费时间。 </错误示例>
<错误示例> 错误的层级选择:
Task(subagent_type="oh-my-claudecode:executor-high", model="opus", prompt="Add a missing semicolon")
为何错误:Opus对于微小修复来说过于昂贵且大材小用。应改用executor-low搭配Haiku。 </错误示例> </示例>
<升级与停止条件>
  • 当直接调用ultrawork(而非通过ralph)时,仅进行轻量级验证——构建通过、测试通过、无新错误
  • 若需要完整持久化和全面架构验证,建议切换到
    ralph
    模式
  • 若任务在多次重试后仍反复失败,应报告问题而非无限重试
  • 当任务存在不明确的依赖关系或冲突需求时,升级给用户处理 </升级与停止条件>
<最终检查清单>
  • 所有并行任务已完成
  • 构建/类型检查通过
  • 受影响的测试通过
  • 未引入新错误 </最终检查清单>
<进阶内容>

Relationship to Other Modes

与其他模式的关系

ralph (persistence wrapper)
 \-- includes: ultrawork (this skill)
     \-- provides: parallel execution only

autopilot (autonomous execution)
 \-- includes: ralph
     \-- includes: ultrawork (this skill)

ecomode (token efficiency)
 \-- modifies: ultrawork's model selection
Ultrawork is the parallelism layer. Ralph adds persistence and verification. Autopilot adds the full lifecycle pipeline. Ecomode adjusts ultrawork's model routing to favor cheaper models. </Advanced>
ralph(持久化包装器)
 \-- 包含: ultrawork(本技能)
     \-- 提供: 仅并行执行

autopilot(自主执行)
 \-- 包含: ralph
     \-- 包含: ultrawork(本技能)

ecomode(Token效率模式)
 \-- 修改: ultrawork的模型选择逻辑
Ultrawork是并行处理层。Ralph增加了持久化和验证功能。Autopilot提供完整的生命周期流水线。Ecomode调整ultrawork的模型路由逻辑,优先选择更经济的模型。 </进阶内容>