ultrawork

Coordinate parallel independent tasks with evidence sharing and pass/fail criteria.

24|2|Updated Mar 12, 2025
One-click install
npx skills add https://github.com/Orinks/AccessiWeather --skill ultrawork-orinks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultrawork
Source: https://github.com/Orinks/AccessiWeather/tree/main/.codex/skills/ultrawork
Command: npx skills add https://github.com/Orinks/AccessiWeather --skill ultrawork-orinks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ultrawork addresses the inefficiency of sequential task execution by providing a parallel execution engine that coordinates multiple tasks, maintains context discipline, and offers smart delegation guidance without enforcing persistence or long-running guarantees.

Core Features & Use Cases

  • Parallel task execution: run multiple independent tasks concurrently to maximize throughput while preserving traceability and context.
  • Lightweight evidence lanes: generate and attach evidence as tasks progress without enrolling in a full pipeline lifecycle.
  • Delegation guidance: suggest when to execute locally vs delegate for maximum throughput and reliability.
  • Lightweight integration: supports optional use with persistence layers like Ralph/autopilot when a verified completion lifecycle is required.

Quick Start

Start Ultrawork on a batch of independent tasks and observe parallel progress.

Frequently Asked Questions about ultrawork

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

FAQPage Schema
How do I run multiple independent tasks in parallel to maximize workflow throughput?

You run multiple independent tasks concurrently using a parallel execution engine that coordinates workflows while preserving context discipline and traceability. It maintains lightweight evidence lanes for progress tracking.

What is a two-track execution model with direct-tool and evidence lanes?

A two-track execution model with direct-tool and evidence lanes is a structured parallel processing approach where one track executes tools directly and the other generates verifiable evidence. This ensures results are verifiable without full persistence guarantees.

How do I verify parallel task results without enforcing full persistence guarantees?

You verify parallel task results without full persistence guarantees by using lightweight evidence lanes that attach evidence as tasks progress. This satisfies functional requirements for explicit acceptance criteria and clear pass/fail verification.

When do I need explicit acceptance criteria for concurrent task management?

You need explicit acceptance criteria for concurrent task management when running workflows where many tasks execute in parallel and results must be verifiable. This ensures clear pass/fail criteria are met across independent parallel lanes.

Can I integrate parallel execution with persistence layers for verified completion lifecycles?

You can integrate parallel execution with persistence layers like Ralph or autopilot when a verified completion lifecycle is required. This provides lightweight integration for optional persistence alongside the concurrent execution engine.

What are the limitations of parallel task execution without long-running guarantees?

The limitations of parallel task execution without long-running guarantees include a lack of full persistence and no enforced long-running stability. It is designed for lightweight evidence sharing and smart delegation rather than durable pipeline lifecycles.