amcos-agent-spawning

Spawn per-team agent instances under AI Maestro governance with pre-flight validation.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-agent-spawning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amcos-agent-spawning
Source: https://github.com/Emasoft/ai-maestro-chief-of-staff/tree/main/skills/amcos-agent-spawning
Command: npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-agent-spawning

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Spawns per-team agent instances to scale workload under AI Maestro governance.

Core Features & Use Cases

  • Pre-flight OAuth validation and eligibility checks prior to spawn
  • Automated agent creation, plugin provisioning, and registry registration
  • Role-based session naming and immediate team notifications
  • Built-in error handling and state-safe recovery paths

Quick Start

Spawn a new Orchestrator agent for project svgbbox by sending a spawn request to the amcos-agent-spawning workflow.

Frequently Asked Questions about amcos-agent-spawning

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

FAQPage Schema
How do I spawn per-team agents for orchestrator or programmer roles?

To spawn per-team agents, submit a spawn request to the workflow, which handles pre-flight OAuth validation, automated agent creation, plugin provisioning, and team registry registration for your specified role.

What pre-flight validation is required before agent spawning under AI Maestro governance?

Pre-flight validation includes OAuth eligibility checks and environment verification to ensure a running tmux session and access to ai-maestro-agents-management and agent-messaging skills before spawning team agents.

Can I spawn agents in a tmux environment without a team registry API?

No, a team registry API is required alongside a running tmux environment and the ai-maestro-agents-management and agent-messaging skills to successfully complete the agent spawning and registration process.

What's the best way to scale workload by spawning multiple team-level agent instances?

The best way to scale workload is by spawning per-team agent instances through the workflow, which ensures automated plugin provisioning, role-based session naming, and immediate team notifications upon creation.

How does state-safe recovery work if agent spawning fails during registration?

State-safe recovery paths are built into the workflow to handle errors during agent creation and registry registration, ensuring failed spawn attempts do not leave orphaned sessions or incomplete registry entries.

Does the agent spawning workflow support multiple roles like integrator and architect?

Yes, the agent spawning workflow supports orchestrator, architect, integrator, and programmer roles, applying role-based session naming and plugin provisioning tailored to each specific team function.