windags-architect

Design directed acyclic graphs of agent nodes for multi-agent workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WinDAGs Architect provides a comprehensive framework to design, execute, mutate, and visualize directed acyclic graphs (DAGs) of skillful AI agents so teams can coordinate multi-agent workflows reliably, safely, and cost-effectively. It addresses ambiguity in planning by supporting vague-node expansion, progressive revelation, mutation strategies, circuit breakers, and cross-wave context management to prevent deadlocks and cascade failures. The skill codifies execution-mode selection, model routing, failure mitigation, and quality-evaluation gates so complex, multi-domain problems can be decomposed and executed as repeatable, auditable workflows.

Core Features & Use Cases

  • Decision frameworks for execution mode selection (local, web, embedded), DAG architecture patterns (sequential, fan-out, iterative refinement), and node commitment levels (committed, tentative, exploratory).
  • Runtime mutation and rescue strategies: circuit breaker configuration, automatic replace/add/split mutations, mutation depth limits, and escalation ladders for human intervention.
  • Model and provider routing guidance (tier-based, cascading, adaptive, RouteLLM patterns), cost-tracking, and integration patterns for durable execution (Temporal), live visualization (ReactFlow + ELKjs), and mixed-provider LLM abstraction.
  • Worked examples: code-review DAGs, vague-node resolution for architectural decisions, and mutation-based recovery for data parsing failures. Real-world use: design, run, and iterate multi-agent pipelines for product engineering, research synthesis, and deployment workflows.

Quick Start

Ask windags-architect to design a dynamic DAG for "Build a portfolio website", recommend execution mode, assign node commitment levels, and produce a wave-by-wave execution plan.

Frequently Asked Questions about windags-architect

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

FAQPage Schema
What is multi-agent DAG orchestration and when do I need it?▼

Multi-agent DAG orchestration coordinates AI agents as a directed acyclic graph to execute complex workflows reliably. You need it when decomposing multi-domain problems into repeatable pipelines requiring cross-wave context management, circuit breakers, and mutation strategies.

How do I design a multi-agent workflow with execution mode selection and node commitment levels?▼

You design multi-agent workflows by selecting execution modes (local, web, embedded), assigning node commitment levels (committed, tentative, exploratory), and choosing DAG architecture patterns like sequential, fan-out, or iterative refinement to produce a wave-by-wave execution plan.

Can I use Temporal and ReactFlow for durable execution and live visualization of agent pipelines?▼

Yes, Temporal enables durable execution of agent pipelines and ReactFlow with ELKjs provides live DAG visualization. The framework supplies integration patterns for both alongside mixed-provider LLM abstraction for routing across different model providers.

What's the best way to handle multi-agent workflow failures and prevent cascade failures in a DAG?▼

Prevent multi-agent cascade failures by configuring circuit breakers, applying automatic replace/add/split mutations, setting mutation depth limits, and using escalation ladders for human intervention to resolve deadlocks across DAG execution waves.

How does model routing work for mixed-provider LLM workflows in a multi-agent DAG?▼

Model routing for mixed-provider LLM workflows uses tier-based, cascading, adaptive, and RouteLLM patterns to direct tasks to appropriate providers. It includes cost-tracking guidance to balance performance and expenses across agent nodes.

Do I need predefined nodes to start designing an agent DAG, or can it handle vague inputs?▼

You do not need predefined nodes because the framework supports vague-node expansion and progressive revelation. It resolves architectural ambiguity by dynamically expanding vague nodes during DAG execution, allowing iterative refinement of multi-agent workflows.