skills.rest
LinXueyuanStdio
LinXueyuanStdioCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Multi-Agent Pipeline Orchestrator

Orchestrate multi-agent parallel development workflows from planning to validated PR creation.

2|Updated Jan 30, 2026
Search Tags:#multi-agent#task orchestration#MCP tooling#code evolution#worktree isolation#PR creation#CI evaluation
One-click install
npx skills add https://github.com/LinXueyuanStdio/viben --skill multi-agent-pipeline-orchestrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Multi-Agent Pipeline Orchestrator
Source: https://github.com/LinXueyuanStdio/viben/tree/main/packages/core/templates/codex/skills/start
Command: npx skills add https://github.com/LinXueyuanStdio/viben --skill multi-agent-pipeline-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the coordination problem of managing multi-agent parallel development so that plans, isolated work, PR creation, and post-validation (reward) happen in the correct order without confusing self-references.

Core Features & Use Cases

  • Parallel work management via worktrees: Plans and delegates implementation to agents running in isolated worktree environments while the orchestrator stays in the main repo.
  • Structured task lifecycle orchestration: Runs a plan phase, triggers a work phase, and then optionally creates PRs and computes rewards.
  • Progress monitoring and guardrails: Provides explicit instructions to monitor swarm status safely, including a self-reference warning to prevent premature termination logic.

Quick Start

Ask the orchestrator to start handling a task by running: viben swarm start <task>

Frequently Asked Questions about Multi-Agent Pipeline Orchestrator

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

FAQPage Schema
How do I orchestrate multi-agent parallel development workflows?▼

Multi-agent parallel development workflows are orchestrated by delegating implementation tasks to agents in isolated worktrees, while the main repository handles task context gathering, plan-phase configuration, and validated PR creation.

What is the best way to manage task context gathering and plan-phase configuration for code evolution?▼

Task context gathering and plan-phase configuration are managed by a structured lifecycle orchestrator that sets up context files, triggers the work phase delegation, and optionally computes rewards for validated code evolution.

How do I use isolated worktrees to coordinate parallel agents for PR creation?▼

Isolated worktrees coordinate parallel agents by applying strict worktree boundaries for code changes, ensuring PR creation and CI evaluation operations occur exclusively in the main repository after the work phase completes.

Does the orchestrator pre-check swarm status during task orchestration?▼

The orchestrator does not pre-check swarm status during task orchestration; it requires safe monitoring behavior with explicit self-reference warnings to prevent premature termination logic before validating PR creation.

Can I trigger parallel work management via worktrees from the command line?▼

Parallel work management via worktrees is triggered from the command line by running the swarm start command with a specific task, initiating the plan phase, work phase delegation, and optional reward computation.

Related Skills

Explore More Software Engineering Skills→
papeete-consulting-labpapeete-consulting-lab

launch-task

Orchestrate software development task launches with kanban state and isolated worktrees.

Official
Advanced
t-stringst-strings

Global Tech Stack

Enforce global tech stack standards in code generation and review tasks.

Official
Basic
makenotionmakenotion
19

tasks-plan

Generate structured implementation plans from Notion task pages.

Official
Intermediate
Veloxia-agencyVeloxia-agency

spawn

Coordinate parallel subagents in isolated git worktrees for shared tasks.

Community
Advanced