ultrawork
Parallel execution engine for high-throughput task completion
- License 许可
- MIT
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- ultrawork
- level
- 4
- description
- Parallel execution engine for high-throughput task completion
- argument-hint
- <task description with parallel work items>
03 SKILL.md 正文
<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
ralphinstead (ralph includes ultrawork) - Task requires a full autonomous pipeline -- use
autopilotinstead (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
ralphwhich 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
modelparameter explicitly when delegating - Read
docs/shared/agent-tiers.mdbefore first delegation for agent selection guidance - Use
run_in_background: truefor operations over ~30 seconds (installs, builds, tests) - Run quick commands (git status, file reads, simple checks) in the foreground </Execution_Policy>
<Steps>
- Read agent reference: Load
docs/shared/agent-tiers.mdfor tier selection - Classify tasks by independence: Identify which tasks can run in parallel vs which have dependencies
- Route to correct tiers:
- Simple lookups/definitions: LOW tier (Haiku)
- Standard implementation: MEDIUM tier (Sonnet)
- Complex analysis/refactoring: HIGH tier (Opus)
- Fire independent tasks simultaneously: Launch all parallel-safe tasks at once
- Run dependent tasks sequentially: Wait for prerequisites before launching dependent work
- Background long operations: Builds, installs, and test suites use
run_in_background: true - 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", 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", model="opus", ...)for complex work - Use
run_in_background: truefor 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", 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", 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, "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", model="opus", prompt="Add a missing semicolon")
Why bad: Opus is expensive overkill for a trivial fix. Use executor 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
ralphmode - 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>
Relationship to Other Modes
ralph (persistence wrapper)
\-- includes: ultrawork (this skill)
\-- provides: parallel execution only
autopilot (autonomous execution)
\-- includes: ralph
\-- includes: ultrawork (this skill)
Ultrawork is the parallelism layer. Ralph adds persistence and verification. Autopilot adds the full lifecycle pipeline. </Advanced>
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.