workflow-runner

Execute agency-orchestrator YAML workflows with role emulation and variable substitution.

Updated Apr 15, 2026

Search Tags:#workflow #orchestration #yaml #execution #topology #ai-agents #multi-role

Ready to run

npx skills add https://github.com/vincent-ng/OpenAgentArm --skill workflow-runner-vincent-ng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-runner
Source: https://github.com/vincent-ng/OpenAgentArm/tree/main/.trae/skills/workflow-runner
Command: npx skills add https://github.com/vincent-ng/OpenAgentArm --skill workflow-runner-vincent-ng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables running agency-orchestrator YAML workflows inside AI tools without requiring external APIs, empowering seamless multi-role orchestration within a single session.

Core Features & Use Cases

Execute agency-orchestrator workflows directly in Claude Code, OpenClaw, or Cursor, including role-based steps, dependencies, and in-session execution.
Topology-driven execution: parse inputs, resolve dependencies, render role prompts, and produce step-level outputs for reuse in later steps.
Use Case: orchestrate product planning, architecture reviews, or multi-stakeholder story creation without leaving the AI tool.

Quick Start

Provide a YAML workflow file to begin a multi-role orchestration within this session.

Frequently Asked Questions about workflow-runner

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

FAQPage Schema

How do I run multi-role YAML workflows inside an AI tool?▼

To run multi-role YAML workflows inside an AI tool, provide a YAML workflow file to the session. The system parses inputs, resolves dependencies, and executes topological sequencing to manage multi-role collaboration without external APIs.

Can I execute agency-orchestrator workflows in Claude Code without API keys?▼

Yes, you can execute agency-orchestrator workflows directly in Claude Code, OpenClaw, or Cursor without API keys. The execution handles role-based steps, variable substitution, and in-session dependency resolution natively.

What is topology-driven execution for multi-role AI collaboration?▼

Topology-driven execution for multi-role AI collaboration is a process that parses workflow inputs, resolves step dependencies, renders role prompts, and produces step-level outputs for reuse in later steps within a single session.

How do I orchestrate product planning and architecture reviews within a single AI session?▼

You can orchestrate product planning and architecture reviews within a single AI session by supplying a YAML workflow. The system enforces per-step role emulation and stores results to produce a final summary.

Does workflow execution support variable substitution from prior step outputs?▼

Yes, workflow execution supports variable substitution from both initial inputs and prior step outputs. It renders role prompts dynamically and stores intermediate results to ensure correct topological sequencing across the workflow.

When should I not use in-session YAML workflow orchestration?▼

You should not use in-session YAML workflow orchestration if your multi-role tasks require external API integrations or stateful execution across multiple disconnected sessions, as this approach is designed for self-contained, single-session dependency resolution.