Use when routing user requests to specialist agents. Trigger with work delegation needs. Loaded by ai-maestro-assistant-manager-agent-main-agent
Routes requests to specialist agents. AMAMA can message directly; routing via AMCOS preferred but not required. 3 governance roles: manager, chief-of-staff, member.
role: 'member'docs_dev/handoffs/ directory exists and is writabledocs_dev/handoffs/Copy this checklist and track your progress:
Routing targets (all role: member, preferably routed via AMCOS for delegation, or directly if urgent):
amaa-) -- architect specializationamoa-) -- orchestrator specializationamia-) -- integrator specialization| Intent Pattern | Route To | Handoff Type |
|---|---|---|
| "design", "plan", "architect", "spec" | AMCOS (for AMAA) | work_request |
| "build", "implement", "create", "code" | AMCOS (for AMOA) | work_request |
| "review", "test", "merge", "deploy" | AMCOS (for AMIA) | work_request |
| "spawn agent", "terminate", "restart" | AMCOS | agent_lifecycle |
| "status", "progress", "update" | Handle directly | none |
| "approve", "reject", "confirm" | Handle directly | approval_response |
See routing-rules.md and handoff-protocol.md in Resources.
| Decision | Handoff File | Message |
|---|---|---|
| Route to specialist | handoff-{uuid}-amama-to-amcos.md | AI Maestro message to AMCOS |
| Handle directly | None | Direct response to user |
| Ambiguous intent | None | Request clarification |
| Error | Resolution |
|---|---|
| Ambiguous intent | Ask user for clarification |
| Target agent unavailable | Queue handoff, notify user, retry |
| Handoff dir missing | Create docs_dev/handoffs/ automatically |
| UUID collision | Generate new UUID and retry |
Input: User says "Design an auth system" Output: Intent "design" → route to AMCOS for AMAA. Handoff saved, message sent.
Input: User says "What's the progress?" Output: Intent "progress" → handle directly. No handoff needed.