multi-agent-orchestration

Orchestrate multi-agent workflows from Kiro specs using Codex and Gemini.

4|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/PeterFile/my-common-skills --skill multi-agent-orchestration-peterfile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent-orchestration
Source: https://github.com/PeterFile/my-common-skills/tree/main/multi-agent-orchestration
Command: npx skills add https://github.com/PeterFile/my-common-skills --skill multi-agent-orchestration-peterfile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill coordinates multi-agent workstreams (Codex for code and Gemini for UI) from a Kiro spec, centralizing dispatch, review, and state synchronization to deliver features end-to-end.

Core Features & Use Cases

  • Orchestrates end-to-end tasks across Codex and Gemini based on a Kiro spec.
  • Maintains coordinated state via AGENT_STATE.json and PROJECT_PULSE.md to reflect decisions, progress, and blockers.
  • Supports deterministic and LLMS-driven modes for orchestration, including auto-dispatch, review, fix loops, and pulse updates.

Quick Start

Initialize orchestration from a spec with the provided tools, then trigger the workflow using the supported commands (Start orchestration from spec at <path>, Run orchestration for <feature>).

Frequently Asked Questions about multi-agent-orchestration

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

FAQPage Schema
How do I orchestrate multi-agent workflows for Codex and Gemini?

Multi-agent orchestration coordinates Codex for code and Gemini for UI from a Kiro spec, centralizing dispatch, review, and state synchronization to deliver features end-to-end. It uses AGENT_STATE.json and PROJECT_PULSE.md to track progress and blockers.

What is the best way to coordinate code and UI generation across multiple AI agents?

Coordinating code and UI generation across agents uses a centralized orchestration model that dispatches tasks from a Kiro spec to Codex and Gemini. It manages auto-dispatch, review, and fix loops to synchronize state across both agents.

How do I start orchestration from a Kiro spec file?

To start orchestration from a Kiro spec, initialize the provided tooling and trigger the workflow using the command Start orchestration from spec at <path>. This dispatches end-to-end feature tasks to Codex and Gemini agents.

Does multi-agent orchestration support automated review and fix loops?

Multi-agent orchestration supports deterministic and LLMS-driven modes that include auto-dispatch, review, fix loops, and pulse updates. This ensures tasks dispatched to Codex and Gemini are synchronized and reviewed automatically.

Can I run orchestration for a specific feature using Codex and Gemini?

You can run orchestration for a specific feature by triggering the workflow with the command Run orchestration for <feature>. This coordinates the end-to-end feature work across Codex and Gemini agents based on your Kiro spec.

How does multi-agent orchestration maintain state across Codex and Gemini agents?

Multi-agent orchestration maintains coordinated state using AGENT_STATE.json and PROJECT_PULSE.md files. These files reflect decisions, progress, and blockers, ensuring synchronized state across dispatched Codex and Gemini workstreams.