workflow-engine

Define machine-readable DAGs for orchestrating multi-agent workflows.

50|32|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/jonathan-vella/azure-agentic-infraops-accelerator --skill workflow-engine-jonathan-vella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-engine
Source: https://github.com/jonathan-vella/azure-agentic-infraops-accelerator/tree/main/.github/skills/workflow-engine
Command: npx skills add https://github.com/jonathan-vella/azure-agentic-infraops-accelerator --skill workflow-engine-jonathan-vella

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a declarative, machine-readable workflow graph that eliminates hardcoded step logic, enabling dynamic routing, state management, and validation of complex agent pipelines.

Core Features & Use Cases

  • Dynamic Routing: Manages complex Directed Acyclic Graphs (DAGs) with conditional edges and parallel execution paths.
  • State Management: Enables resuming workflows from saved session states.
  • Validation: Ensures proper dependencies and outputs for all workflow steps.
  • Use Case: The Conductor agent uses this Skill to determine the next logical step in a multi-agent infrastructure deployment process, routing based on previous outcomes and human approvals.

Quick Start

Use the workflow-engine skill to validate the current step against the defined workflow graph.

Frequently Asked Questions about workflow-engine

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

FAQPage Schema
How do I orchestrate complex multi-agent workflows with conditional routing?

Multi-agent workflow orchestration is handled by defining a machine-readable Directed Acyclic Graph (DAG) that specifies node types, edge conditions, and parallel execution paths to dynamically route agents without hardcoding step logic.

What is a declarative workflow graph and when do I need it for agent pipelines?

A declarative workflow graph is a machine-readable structure that defines execution logic for agent pipelines. You need it when managing complex routing, state management, and validation to eliminate hardcoded step dependencies in multi-agent infrastructure.

How do I resume an agent pipeline from a saved session state?

Agent pipeline resumption from saved session states is enabled through the workflow graph's state management capabilities, allowing the Conductor to validate the current step and determine the next logical action based on previous outcomes.

Can I use parallel execution paths and human approval gates in a workflow DAG?

Parallel execution paths and human approval gates are fully supported node types within the workflow DAG, allowing the Conductor agent to route infrastructure deployment steps based on previous outcomes and manual approvals.

Does the workflow engine validate dependencies and outputs for all pipeline steps?

Workflow engine validation ensures proper dependencies and outputs for all workflow steps, verifying the structural integrity of the Directed Acyclic Graph before the Conductor agent routes any multi-agent execution.

Why use a declarative DAG instead of hardcoded step logic for pipeline orchestration?

Using a declarative DAG for pipeline orchestration eliminates hardcoded step logic, enabling dynamic routing, state management, and validation of complex agent pipelines while allowing workflows to resume from saved states.