coordinate

Orchestrate parallel AMP agents via tmux for coordinated workflows.

5|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/humblemuzzu/ghosttyyy --skill coordinate-humblemuzzu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinate
Source: https://github.com/humblemuzzu/ghosttyyy/tree/main/pi-setup/config-skills/coordinate
Command: npx skills add https://github.com/humblemuzzu/ghosttyyy --skill coordinate-humblemuzzu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate parallel AMP agents to coordinate a complex, multi-hour workflow across a single coordination layer, reducing manual overhead and miscommunication.

Core Features & Use Cases

  • Bidirectional tmux communication between a coordinator and multiple agents to manage tasks, progress, and results in real time.
  • Spawn and manage independent agents for long-running runs without blocking the main workflow.
  • Centralized control and monitoring with safe cleanup and fallback procedures to handle agent failures or deadlocks.

Quick Start

Invoke the spawn script to initialize AMP agents and begin coordinated messaging via tmux.

Frequently Asked Questions about coordinate

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

FAQPage Schema
How do I orchestrate parallel multi-agent workflows in tmux?

You can orchestrate parallel AMP agents in tmux by using bidirectional communication to manage tasks, progress, and results in real time without blocking the main workflow.

What is the best way to manage long-running autonomous agents in parallel?

Managing long-running autonomous agents requires a centralized control layer that provides inter-agent messaging, real-time monitoring, and safe cleanup procedures to handle agent failures or deadlocks.

Can I spawn independent agents without blocking my main workflow?

Yes, you can spawn and manage independent agents for long-running tasks without blocking the main workflow by utilizing tmux orchestration and centralized control commands.

How does inter-agent messaging work across coordinated tmux sessions?

Inter-agent messaging works via bidirectional tmux communication between a coordinator and multiple agents, enabling centralized task management, progress tracking, and safe handoffs.

What happens if an agent fails or deadlocks during a parallel workflow?

If an agent fails or deadlocks, the orchestration layer applies safeguards for centralized monitoring, fallback procedures, and safe cleanup to handle the failure without disrupting the entire workflow.

Do I need any dependencies to coordinate multi-agent tmux workflows?

No external dependencies are required to coordinate multi-agent tmux workflows, as the orchestration relies on internal spawn tooling and tmux for agent management and communication.