dmux-workflows

Plan parallel agent work with ownership, work splits, and merge order.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/espensev/ai-skills --skill dmux-workflows-espensev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dmux-workflows
Source: https://github.com/espensev/ai-skills/tree/main/codex-skills/skills/dmux-workflows
Command: npx skills add https://github.com/espensev/ai-skills --skill dmux-workflows-espensev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate parallel agent work for large tasks by defining clear work splits, ownership, and merge order, enabling efficient delegation and orchestration.

Core Features & Use Cases

  • Define worker rosters, owned files, and merge sequencing for parallel tasks.
  • Support optional external orchestration (dmux) or git worktrees to coordinate multiple subagents.
  • Provide structured verification points and owner responsibility to prevent overlaps.

Quick Start

Coordinate parallel agent tasks by outlining ownership, work splits, and merge order for a given project.

Frequently Asked Questions about dmux-workflows

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

FAQPage Schema
How do I coordinate parallel agents to avoid file conflicts during task execution?

Coordinate parallel agents by defining explicit worker rosters, owned files, and merge sequencing. This structured ownership prevents overlaps and ensures multiple agents execute delegated tasks without modifying the same files.

What is the best way to decompose large tasks for parallel agent execution?

Decompose large tasks by splitting them into clear work segments and mapping each segment to a specific owner. Establishing explicit integration steps and verification points ensures subagents execute their designated work safely.

Can I use git worktrees to orchestrate parallel subagents instead of dmux?

Yes, you can use git worktrees to orchestrate parallel subagents. The planning approach supports optional external orchestration through dmux or worktrees to coordinate multiple agents while avoiding execution conflicts.

How do I define merge order for parallel workflows with multiple agents?

Define merge order by establishing clear work splits and sequencing rules for the workers involved. Setting explicit integration steps and verification points allows you to safely merge the completed work from multiple agents.

When should I not use parallel orchestration for agent workflows?

Avoid parallel orchestration when tasks lack clear ownership boundaries or cannot be safely decomposed. If work splits overlap or integration steps cannot be explicitly verified, coordinated parallel execution becomes unsafe and prone to conflicts.