orchestrate

Spawn parallel worker terminals to execute multi-domain tasks concurrently.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lofidonut3/oh-my-speckit --skill orchestrate-lofidonut3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/lofidonut3/oh-my-speckit/tree/main/skills/orchestrate
Command: npx skills add https://github.com/lofidonut3/oh-my-speckit --skill orchestrate-lofidonut3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn parallel worker terminals to execute multi-domain tasks concurrently by dedicating a separate OpenCode instance per domain.

Core Features & Use Cases

  • Parallel multi-domain task execution: 1 domain = 1 worker terminal; tasks run concurrently.
  • Depth-limited orchestration: maximum orchestration depth is 2 to prevent uncontrolled spawning.
  • Environment controls: ORCH_DEPTH and ORCH_MAX_DEPTH govern worker behavior and depth limits.
  • Windows/WSL compatibility: supports spawning workers via Windows Terminal or tmux in WSL.
  • Fallback and monitoring: collects results to a shared workspace; supports prompt-based fallbacks if opencode unavailable.
  • Integration readiness: compatible with Speckit workflow steps for planning, executing, and verifying tasks.

Quick Start

Use /orchestrate to spawn workers for 3+ independent tasks spanning 2+ domains. If you have a plan file, reference it with execute.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I run parallel tasks across multiple domains concurrently?

To run parallel tasks across multiple domains, you can spawn dedicated worker terminals that execute independent tasks concurrently. This orchestration approach assigns one worker per domain to process tasks without strong sequential dependencies.

When should I use parallel worker terminals for task orchestration?

Parallel worker terminals are needed when you have at least three independent tasks spanning two or more domains. This orchestration method is designed for scenarios where tasks can run concurrently without strong sequential dependencies.

How do I spawn parallel workers using tmux in WSL?

To spawn parallel workers in WSL, the orchestration tool supports environment controls and tmux to launch dedicated terminal sessions. It monitors these domain-specific workers and collects their results into a shared workspace.

Does parallel orchestration work on Windows without tmux?

Parallel orchestration supports Windows environments by spawning workers through Windows Terminal or via WSL using tmux. This ensures cross-platform compatibility for executing concurrent multi-domain tasks.

What are the depth limitations for spawning parallel workers?

The maximum orchestration depth is strictly limited to 2 to prevent uncontrolled spawning of worker terminals. The ORCH_DEPTH and ORCH_MAX_DEPTH environment variables govern this worker behavior and enforce the depth limits.

What happens if opencode is unavailable during multi-domain task execution?

If opencode is unavailable during multi-domain task execution, the orchestration system supports prompt-based fallbacks to continue operations. It also monitors the workers and collects all resulting outputs to a shared workspace.