zenflow

Orchestrate multi-agent LLM workflows with declarative YAML DAGs and centralized coordination.

41|5|Updated May 7, 2026
One-click install
npx skills add https://github.com/zendev-sh/zenflow --skill zenflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zenflow
Source: https://github.com/zendev-sh/zenflow/tree/main
Command: npx skills add https://github.com/zendev-sh/zenflow --skill zenflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the complexity of managing multi-agent LLM pipelines by providing a declarative, race-safe, and observable framework for orchestrating agent workflows.

Core Features & Use Cases

  • Declarative YAML Workflows: Define complex DAGs with parallel fan-out, loops, and conditions without writing imperative control flow code.
  • Hub-and-Spoke Messaging: Ensures reliable, race-safe communication between agents via a centralized coordinator, preventing silent message loss.
  • Use Case: Automate a software development lifecycle where a planner agent defines tasks, a coder agent implements features, and a reviewer agent validates changes, all coordinated through a single YAML specification.

Quick Start

Use the zenflow skill to execute the workflow defined in review.yaml using the gemini-3-pro-preview model.

Frequently Asked Questions about zenflow

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

FAQPage Schema
How do I orchestrate multi-agent LLM workflows without writing imperative control flow code?

You can orchestrate multi-agent LLM workflows declaratively by defining complex DAGs with parallel fan-out, loops, and conditions in YAML, eliminating the need for imperative control flow code.

How does race-safe message delivery work between distributed LLM agents?

Race-safe message delivery between agents is handled through a hub-and-spoke messaging architecture using a centralized coordinator, which prevents silent message loss during distributed workflow execution.

Can I define branching and loops in a YAML workflow for complex automation tasks?

Yes, you can define branching, loops, and conditions directly within a declarative YAML specification to manage complex automation tasks across distributed agent steps with persistent state management.

Does zenflow integrate with native MCP tools and output structured observability events?

zenflow supports native MCP tool integration and outputs structured NDJSON events, providing observability for multi-agent pipelines while maintaining persistent state across distributed steps.

What is the best way to automate a software development lifecycle using multiple LLM agents?

The best way is to define the lifecycle in a single YAML specification where a planner agent defines tasks, a coder implements features, and a reviewer validates changes, all coordinated by a centralized executor.

When should I not use a declarative YAML executor for multi-agent orchestration?

You should avoid declarative YAML orchestration if your multi-agent tasks do not require complex DAGs, branching, loops, or persistent state management across distributed steps and can be handled by simple sequential calls.