parallel-dev

Orchestrate parallel development by spawning isolated worktrees for concurrent subtasks.

4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/EZotoff/ez-omo-config --skill parallel-dev-ezotoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-dev
Source: https://github.com/EZotoff/ez-omo-config/tree/main/skills/parallel-dev
Command: npx skills add https://github.com/EZotoff/ez-omo-config --skill parallel-dev-ezotoff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and control multi-agent parallel development across isolated worktrees to reduce manual orchestration, avoid destructive git actions, and streamline merge handoff while preserving runtime isolation and auditability.

Core Features & Use Cases

  • Decision framework: mandatory pre-flight checks to determine when parallelization is beneficial and safe.
  • Controlled spawning: spawn isolated worktrees using worktree_create with a hard MAX_PARALLEL=4 limit to prevent resource exhaustion.
  • Durable dispatch and monitoring: deliver tasks via persisted task files or tmux send-keys, monitor per-branch JSON state files under ~/.local/share/opencode/worktree-state/<project-id>/, and enforce timeouts and cleanup.
  • Safe merge handoff: prefer agent self-triggered merges via the merge-agent skill and coordinator fallback using tmux send-keys; avoid duplicating merge internals.
  • Failure handling and guardrails: timeout cleanup, preserve failed worktrees for debugging, and strict prohibitions on writing canonical state or implementing agent-to-agent messaging.

Quick Start

Invoke the parallel-dev coordinator with the /parallel-dev trigger to run the decision framework, spawn permitted worktrees, dispatch tasks via task files, monitor state until completion, and trigger merges.

Frequently Asked Questions about parallel-dev

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

FAQPage Schema
How do I run parallel development across multiple isolated git worktrees?

To run parallel development, you spawn isolated git worktrees for multiple agents to execute concurrent subtasks, dispatching tasks via durable files or tmux send-keys while monitoring JSON state files to coordinate completion.

What is the maximum number of parallel agents I can spawn for concurrent task dispatch?

The maximum number of parallel agents you can spawn is four, enforced by a hard MAX_PARALLEL=4 limit to prevent resource exhaustion during multi-agent worktree orchestration.

How do I monitor state for parallel agents working in separate worktrees?

You monitor state for parallel agents by reading per-worktree JSON state files stored under the ~/.local/share/opencode/worktree-state/<project-id>/ directory to track progress and enforce timeouts.

What is the safest way to merge branches completed by parallel development agents?

The safest way to merge branches is to prefer agent self-triggered merges via the merge-agent skill, falling back to coordinator-triggered merges using tmux send-keys to avoid destructive git actions.

What happens to failed worktrees when a parallel subtask encounters an error?

When a parallel subtask fails, the orchestration framework runs timeout cleanup but preserves the failed worktrees, allowing you to debug the isolated branch state without losing context.

When should I not use parallel worktree orchestration for software engineering tasks?

You should not use parallel worktree orchestration when subtasks are not independent, as the framework requires features, tests, or bug fixes to be safely split into separate branches to avoid destructive git actions.