ultrawork

Schedule and execute independent tasks in parallel across multiple agents.

2|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/chrisxue90/oh-my-qwencode --skill ultrawork-chrisxue90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultrawork
Source: https://github.com/chrisxue90/oh-my-qwencode/tree/main/skills/ultrawork
Command: npx skills add https://github.com/chrisxue90/oh-my-qwencode --skill ultrawork-chrisxue90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultrawork reduces idle time by executing multiple independent tasks in parallel, allowing faster completion without built-in persistence or verification loops.

Core Features & Use Cases

  • Parallel task execution across multiple agents for independent work
  • Explicit model routing by passing the model parameter during delegation
  • Optional background execution for long-running operations and quick foreground checks
  • Lightweight lifecycle guidance and state hints (without full persistence)

Quick Start

Delegate multiple independent tasks to ultrawork and let them run in parallel.

Frequently Asked Questions about ultrawork

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple tasks in parallel across different agents?

Parallel task execution works by scheduling and running independent tasks concurrently across multiple agents to reduce idle time and total completion time. The orchestrator delegates work without built-in persistence or verification loops.

Can I route specific models when delegating tasks for parallel execution?

Yes, you can explicitly route specific models during parallel task delegation by passing the model parameter. This allows you to assign specific models to individual concurrent tasks when orchestrating independent work across multiple agents.

What is the best way to handle long-running operations in a parallel workflow?

The best way to handle long-running operations in a parallel workflow is using optional background execution. This allows long-running tasks to process concurrently while you perform quick foreground checks for immediate results.

Does parallel task orchestration verify results or persist state automatically?

No, parallel task orchestration does not include built-in persistence or verification loops. It provides lightweight lifecycle guidance and state hints, meaning you must manually manage completion verification and final results.

When should I not use parallel execution for agent workflows?

You should avoid parallel execution for agent workflows when tasks are dependent on each other or require strict verification loops. It is designed for independent concurrent work without persistence, so sequential execution is better for dependent operations.