Yaml Based Declarative Agent Definition With Structured Execution

via “multi-agent orchestration with hierarchical agent types”

Google's agent framework — tool use, multi-agent orchestration, Google service integrations.

Unique: Implements three distinct agent execution patterns (Loop, Sequential, Parallel) as first-class types with explicit state hierarchy and context propagation, rather than generic agent composition. Each pattern has dedicated configuration classes (LoopAgentConfig, SequentialAgentConfig, ParallelAgentConfig) that enforce pattern-specific semantics and prevent misuse.

vs others: More structured than LangGraph's flexible graph approach — enforces specific execution semantics upfront, reducing debugging complexity for common multi-agent patterns at the cost of less flexibility for custom topologies

via “configuration-driven agent and task definition with yaml”

CrewAI multi-agent collaboration example templates.

Unique: Implements configuration-driven agent definition through YAML files (gamedesign.yaml pattern) that specify agent roles, goals, backstories, tools, and task dependencies. The framework parses YAML at runtime and instantiates agents without code changes, enabling non-developers to modify agent behavior.

vs others: More accessible than code-based agent definition; enables configuration changes without developer involvement

via “agent skills and sub-agent delegation with hierarchical task decomposition”

An open-source AI agent that brings the power of Gemini directly into your terminal.

Unique: Implements a skill registry system that allows pre-configured agents to be invoked as tools, enabling hierarchical task decomposition. Each skill is a complete agent configuration with its own instructions, tools, and model settings.

vs others: More modular than monolithic agents because skills can be developed, tested, and reused independently, enabling teams to build complex agent systems from composable components.

via “declarative graph-based agent orchestration via stategraph api”

Build resilient language agents as graphs.

Unique: Uses a Bulk Synchronous Parallel (BSP) execution model inspired by Google's Pregel paper, enabling deterministic, step-level state snapshots and resumable execution. Unlike imperative frameworks, StateGraph separates graph topology from execution semantics, allowing the same graph definition to run locally, remotely, or distributed without code changes.

vs others: Provides lower-level control than high-level agent frameworks (e.g., LangChain agents) while maintaining declarative clarity, enabling both rapid prototyping and production-grade customization that imperative orchestration libraries cannot match.

via “agents.md operating rules and conditional logic”

162 production-ready AI agent templates for OpenClaw. SOUL.md configs across 19 categories. Submit yours!

Unique: Implements AGENTS.md as an optional extension to SOUL.md for defining complex operating rules and conditional logic in declarative markdown format. This enables agents to implement sophisticated workflows without code while keeping logic version-controllable and auditable.

vs others: More expressive than SOUL.md alone because it supports conditional logic; simpler than code-based agent frameworks because logic is defined in markdown rather than Python/JavaScript.

via “multi-agent swarm orchestration with role-based task delegation”

Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.

Unique: Uses a declarative AGENTS.md manifest to define agent roles, capabilities, and delegation rules, enabling task routing without code changes. Agents maintain separate memory and tool sets while sharing a common knowledge hub, enabling specialization without isolation. The framework provides explicit inter-agent communication patterns rather than requiring agents to coordinate through shared state.

vs others: Unlike LangChain's agent teams (which require code-based agent definitions) or AutoGen (which uses a message-passing architecture), Antigravity's multi-agent system uses declarative role definitions in AGENTS.md, making it easier to modify agent responsibilities without code changes. The shared knowledge hub approach is more efficient than message-passing for large agent swarms.

via “declarative agent composition and template instantiation”

Hi HN,I’m Vincent from Aden. We spent 4 years building ERP automation for construction (PO/invoice reconciliation). We had real enterprise customers but hit a technical wall: Chatbots aren't for real work. Accountants don't want to chat; they want the ledger reconciled while they slee

Unique: Provides declarative agent templates with parameterized behavior, allowing runtime instantiation of agent variants without code changes

vs others: More flexible than hardcoded agent factories, but requires learning framework-specific template syntax unlike generic dependency injection containers

via “command-to-agent-to-skill orchestration pipeline”

from vibe coding to agentic engineering - practice makes claude perfect

Unique: Uses a declarative markdown-based command registry combined with 17+ lifecycle hooks for deterministic agent automation, enabling runtime behavior modification without code changes. Unlike monolithic agent frameworks, this separates command definition (what to do), agent selection (who does it), and skill execution (how to do it) into independently testable layers.

vs others: Provides more granular control over agent execution than frameworks like LangChain agents or AutoGPT, which typically use single-layer command routing; the three-tier model enables skill reuse across multiple agents and lifecycle-based automation that would require custom middleware in other frameworks.

via “yaml-based configuration system with agent and workflow definitions”

MS-Agent: a lightweight framework to empower agentic execution of complex tasks

Unique: Implements configuration-driven agent instantiation through AgentLoader factory, enabling agents to be created from YAML without code. Supports environment-based configuration overrides for multi-environment deployments (dev/staging/prod).

vs others: More accessible than code-based configuration for non-technical users; better than hardcoded configurations for managing multiple environments; enables configuration sharing and standardization across teams

via “app.runtime.yaml manifest-driven application configuration and deployment”

An Open Agent Computer for ANY digital work.

Unique: Implements manifest-driven configuration as primary application definition mechanism, where app.runtime.yaml is the source of truth for agent capabilities, tools, and workspace structure. Manifests are parsed and validated by runtime at startup, enabling configuration-driven agent development.

vs others: Provides declarative configuration-driven agent definition through YAML manifests, whereas most agent frameworks require programmatic configuration in code, limiting accessibility to non-developers.

via “agent configuration and orchestration with yaml/json policy files”

Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.

Unique: Provides declarative YAML/JSON-based agent configuration with built-in orchestration and agent composition support, allowing non-technical users to define and route between agents without code, with capability-based access control integrated into configuration schema

vs others: More accessible than code-based agent definition for non-technical users, though less flexible than programmatic APIs for complex conditional logic or dynamic behavior

via “yaml-based agent workflow definition”

Hey HN, we're Jon and Kristiane, and we're building Orloj (https://orloj.dev), an open-source orchestration runtime for multi-agent AI systems. You define agents, tools, policies, and workflows in declarative YAML manifests, and Orloj handles scheduling, execution, governance, an

Unique: Applies GitOps and infrastructure-as-code patterns to agent workflows, enabling version-controlled, peer-reviewed agent configurations rather than treating agent logic as ephemeral code

vs others: Differs from LangChain/LlamaIndex by prioritizing declarative YAML configuration over imperative Python chains, enabling non-engineers to modify agent behavior and supporting GitOps deployment patterns

via “yaml-based agent configuration with declarative syntax”

I'm one of the creators of The Edge Agent (TEA). We built this because we needed a way to deploy agents that was verifiable and robust enough for production/edge cases, moving away from loose scripts.The architecture aims to solve critical gaps in deterministic orchestration identified by

Unique: Uses YAML as the primary agent definition language rather than Python/JavaScript DSLs, lowering barrier to entry for non-developers while maintaining full integration with 110 built-in tools

vs others: Simpler configuration syntax than LangChain's Python-based agent builders or AutoGen's multi-agent frameworks, enabling faster iteration for configuration-driven use cases

via “agent configuration and capability declaration”

We were both genuinely impressed by Claude Code after it helped each of us fix nasty CI problems overnight. Doing those fixes manually would have taken days.After that experience, we each found ourselves struggling through Ctrl+Tab through multiple Claude Code windows in our terminals. While we enjo

Unique: Declarative agent configuration with capability-based routing, allowing tasks to be matched to agents based on declared capabilities rather than manual assignment. Likely uses a schema validation library (JSON Schema or similar) to ensure configuration correctness.

vs others: Simpler than programmatic agent setup and enables non-technical users to configure agent fleets through configuration files

via “three-file markdown schema for agent decomposition”

Show HN: Agent Kernel – Three Markdown files that make any AI agent stateful

Unique: Proposes a minimal three-file markdown schema (metadata, context, history) that decouples agent configuration from runtime state from interaction logs, enabling modular state inspection and manipulation without requiring a unified database schema.

vs others: More structured than ad-hoc markdown logging but simpler than formal state machines or event sourcing systems; enables git-based workflows while providing enough structure for tooling to parse and manipulate state reliably.

via “yaml-based declarative agent definition with structured execution”

** is an open source command line tool designed to be a simple yet powerful platform for creating and executing MCP integrated LLM-based agents.

Unique: Uses YAML-based declarative definitions rather than programmatic agent builders, enabling non-developers to define agents and making agent behavior transparent and auditable through version control

vs others: More auditable and reproducible than LangChain/LlamaIndex agents because agent logic is declarative YAML rather than embedded in Python code, enabling easier compliance and debugging

via “yaml-based workflow definition with low-code agent configuration”

A framework for building multi-agent AI systems with workflows, tool integrations, and memory. #opensource

Unique: Implements YAML as a first-class configuration format with full schema support for agents, tasks, and workflows, rather than as an afterthought. YAML configurations are validated and can be introspected programmatically, enabling tooling and IDE support.

vs others: More complete YAML support than CrewAI's basic config files; lower barrier to entry than AutoGen's programmatic-only approach

via “pre-execution action planning with explicit step declaration”

Open source framework for building agents that pre-express their planned actions, share their progress and can be interrupted by a human. [#opensource](https://github.com/portiaAI/portia-sdk-python)

Unique: Implements a mandatory planning phase where agents must declare actions before execution, creating a checkpoint for human review rather than relying on post-hoc logging or trace inspection

vs others: Differs from standard LLM agents (Anthropic Claude, OpenAI Assistants) which execute actions reactively; Portia's pre-declaration model enables interruption and validation before side effects occur

via “yaml-driven multi-agent workflow orchestration”

Communicative agents for software development

Unique: Configuration-driven architecture where YAML files define complete agent workflows without code, combined with domain-agnostic runtime that executes identical orchestration logic across software development, data visualization, 3D generation, game development, and video creation domains. Unlike Langchain/LlamaIndex which require Python chains, ChatDev 2.0 separates workflow definition from execution runtime.

vs others: Eliminates code-based agent choreography entirely through YAML configuration, enabling non-technical users to compose multi-agent workflows that Langchain/Crew AI require Python expertise to define.

via “declarative agent configuration with yaml/json specifications”

Multi Agent SDK with pluggable, modular components

Unique: Separates agent configuration from code through declarative specifications that map directly to the pluggable component architecture, enabling configuration-driven agent instantiation without code changes

vs others: More flexible than hardcoded agent initialization because configuration can be changed without redeployment; more maintainable than programmatic agent building because configurations are version-controlled and auditable