parallel-dispatch-dag

What problem does it solve?

This Skill prevents agents from executing interdependent scope tasks out of order by constructing and validating a dependency DAG so each parallel “level” runs only after its required predecessors complete.

Core Features & Use Cases

• DAG construction from scope cards: Converts each scope card into a node (with agent type, scope, phase, and type) and turns hard dependencies into directed edges.
• Topological level scheduling: Performs a topological sort and groups nodes into dependency “levels” so all nodes in the same level can run concurrently.
• Safety validation before execution: Detects cycles, blocks dangling references, enforces MECE write-scope boundaries via the ownership skill, and applies phase ordering constraints (e.g., DESIGN before BUILD).
• Failure-aware dynamic re-planning: Invalidates downstream dependents on failure, re-decomposes only the affected sub-tree, and resumes from the correct replanned level.
• Execution protocol with merge points: Creates git worktrees for write-nodes, dispatches per level, merges after each level, and continues through phase transitions according to orchestrate.toml rules.

Quick Start

Use parallel-dispatch-dag after parallel-dispatch-decomposition generates scope cards, so the system builds a validated dependency graph and dispatches independent scopes in parallel level-by-level.