manager-orchestrator

Coordinate multiple project-level AI orchestrators and aggregate status updates across workstreams.

4|Updated Dec 7, 2025
One-click install
npx skills add https://github.com/grigb/gas-prompt-library --skill manager-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manager-orchestrator
Source: https://github.com/grigb/gas-prompt-library/tree/main/agents/agent-manager-orchestrator
Command: npx skills add https://github.com/grigb/gas-prompt-library --skill manager-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing complex, multi-project AI agent ecosystems by providing a centralized control layer that coordinates orchestrators rather than individual workers.

Core Features & Use Cases

  • Portfolio Orchestration: Manages multiple project-level orchestrators within a single native tree, ensuring visibility and interruptibility.
  • Health-Based Monitoring: Uses beacon-based status tracking to monitor project health and resolve cross-project dependencies or conflicts.
  • Use Case: A project manager overseeing three separate development workstreams can use this skill to aggregate status, resolve resource conflicts between teams, and ensure all orchestrators remain within safety limits.

Quick Start

Invoke the manager-orchestrator to initialize the portfolio view and begin monitoring active project beacons.

Frequently Asked Questions about manager-orchestrator

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

FAQPage Schema
How do I coordinate multiple AI orchestrators managing separate development workstreams?

You can coordinate multiple AI orchestrators by using a centralized portfolio control layer that manages cross-project dependencies, resolves resource conflicts, and aggregates status updates within a single native tree structure.

What is beacon-based state management for multi-project AI agent coordination?

Beacon-based state management is a non-polling communication pattern used to monitor project health, track status updates, and ensure visibility across workstreams while maintaining strict safety protocols.

How do I resolve resource conflicts between multiple AI agents working on different projects?

Resource conflicts between AI agents are resolved by a centralized orchestration layer that monitors project health via beacons and enforces safety limits to manage cross-project dependencies effectively.

Can I use portfolio-level orchestration to monitor the health of separate development workstreams?

Yes, portfolio-level orchestration monitors the health of separate development workstreams by tracking beacon-based status updates and aggregating them into a centralized view for interruptibility and conflict resolution.

When do I need a centralized control layer for AI agent ecosystems instead of managing individual workers?

You need a centralized control layer when managing complex, multi-project AI agent ecosystems where coordinating orchestrators directly is required to handle cross-project dependencies and resource governance.

What are the limitations of using a portfolio orchestrator for multi-project AI coordination?

The portfolio orchestrator requires strict adherence to safety protocols, beacon-based state management, and non-polling communication patterns, meaning your ecosystem must conform to these structural constraints to function properly.