dag-runtime

Execute DAG workflows with concurrent agent isolation, permissions, retries, and execution tracing.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill dag-runtime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dag-runtime
Source: https://github.com/curiositech/port-daddy/tree/main/skills/dag-runtime
Command: npx skills add https://github.com/curiositech/port-daddy --skill dag-runtime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates and executes planned Directed Acyclic Graph (DAG) workflows to coordinate concurrent agents, enforce isolation and permissions, and provide full execution tracing and failure recovery so teams can run complex multi-node tasks reliably.

Core Features & Use Cases

  • Parallel wave processing: Advance DAGs in waves with deterministic progression, allowing non-dependent nodes to run concurrently for speed.
  • Agent spawning and isolation: Spawn agents per node with selectable isolation levels (container, process, context, or none) to balance security and functionality.
  • Permission enforcement and inheritance: Ensure child node permissions are intersected with parent permissions to prevent permission creep.
  • Failure escalation and retry policies: Classify failures (timeouts, schema errors, permissions, missing skills) and apply configurable retries, backoff, or human escalation.
  • Execution tracing and salvage: Record node-level traces (model, tokens, cost, duration) and recover work from crashed agents for resumable runs.
  • Use Case: Run a multi-wave security analysis DAG that isolates risky code execution in containers, retries malformed outputs with schema reminders, and composes a final report from available partial outputs.

Quick Start

Execute the DAG named "security-scan" with parallel waves, container isolation for risky nodes, and retry policies applied.

Frequently Asked Questions about dag-runtime

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

FAQPage Schema
How do I execute DAG workflows with parallel agent orchestration?

DAG workflow execution coordinates concurrent agent tasks by advancing nodes in parallel waves, allowing non-dependent nodes to run concurrently for faster deterministic processing. Each node spawns an isolated agent with enforced permissions and configurable retry policies.

What is the best way to isolate risky nodes during parallel DAG execution?

Node isolation during parallel DAG execution supports selectable levels including container, process, context, or no isolation. Container isolation is recommended for risky nodes like untrusted code execution, balancing security with functionality while maintaining deterministic progression.

How do permission inheritance checks work when spawning child agents in a DAG?

Permission inheritance in DAG agent spawning intersects child node permissions with parent node permissions to prevent permission creep. This ensures child agents never exceed the access rights of their parent nodes during parallel execution.

Can I retry failed DAG nodes with backoff and human escalation?

Failed DAG nodes support configurable retry policies with backoff and human escalation. Failures are classified by type—timeouts, schema errors, permissions, or missing skills—allowing targeted retry strategies or escalation when retries are exhausted.

Does DAG execution tracing record token usage and cost per node?

DAG execution tracing records node-level metrics including model used, token counts, cost, and duration. Traced data supports execution salvage, allowing recovery of work from crashed agents for resumable workflow runs.

What happens to partial outputs when an agent crashes during multi-wave DAG processing?

When agents crash during multi-wave DAG processing, execution tracing salvages recorded work from completed nodes. Partial outputs are recovered and composed into final results, enabling resumable runs without restarting the entire workflow.