メニュー
Use when coordinating team members across agent sessions, assigning roles, managing messaging, and maintaining team status. Trigger with team formation, updates, or coordination needs. Loaded by ai-maestro-chief-of-staff-main-agent
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when applying or checking GitHub labels for agent assignment and status tracking. Trigger with label management or taxonomy lookup requests. Loaded by ai-maestro-chief-of-staff-main-agent
CHIEF-OF-STAFF's role in the PRRD / TRDD / Kanban workflow. COS does NOT own kanban columns directly — it ROUTES messages and proposals between the team layer (ORCH/ARCH/INT/MEMBER) and the governance layer (MANAGER). Use when COS forwards a PRRD proposal, relays approval decisions, broadcasts TRDD status updates, or aggregates team status for AMAMA.
Use when sending failure notifications after operation errors. Trigger with failure events, error reporting, or incident notification. Loaded by ai-maestro-chief-of-staff-main-agent
Use when managing team registry, inter-agent messaging, role boundaries, or sub-agent delegation. Trigger with team coordination tasks. Loaded by ai-maestro-chief-of-staff-main-agent
Use when requesting or processing agent acknowledgments before proceeding with operations. Trigger with acknowledgment requests or ACK timeout handling. Loaded by ai-maestro-chief-of-staff-main-agent
Use when replacing a failed agent with a new instance. Trigger with agent replacement or failover events. Loaded by ai-maestro-chief-of-staff-main-agent
| name | amcos-team-coordination |
| description | Use when coordinating team members across agent sessions, assigning roles, managing messaging, and maintaining team status. Trigger with team formation, updates, or coordination needs. Loaded by ai-maestro-chief-of-staff-main-agent |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Requires AI Maestro messaging API access, session name resolution, and inter-agent communication capabilities. Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Team coordination manages distributed agent teams, assigns roles, coordinates messaging between members, and maintains awareness of all active teammates and their current status.
Copy this checklist and track your progress:
| Coordination Type | Output |
|---|---|
| Team formation | New team created, agents assigned |
| Role assignment | Agent roles updated, registry modified |
| Status sync | All agents aligned on current state |
When/Steps: Identify role, match capabilities, send assignment message, confirm acceptance, update roster.
When/Steps: Identify recipients, compose with priority, send via AI Maestro API, confirm delivery, log.
See team-messaging in Resources below
When/Steps: Poll for active sessions, query status, update roster, identify inactive agents, flag issues.
Input: "Assign agent libs-svg-renderer the role of QA lead"
amp-send.sh libs-svg-renderer "Role Assignment: QA Lead" \
"You are assigned QA lead for the SVG pipeline team. Please acknowledge."
Expected result: Agent receives role assignment, replies with acknowledgment, roster updated.
| Issue | Resolution |
|---|---|
| Agent does not respond to role | Retry with higher priority, check if active, escalate after 3 attempts |
| Messages not delivered | Verify AI Maestro running, check session names, validate format |
| Team roster stale | Force refresh via polling, clear and rebuild, verify registry |