メニュー
Use when an agent needs to be transferred between teams. Trigger with transfer requests, transfer approvals, or transfer status checks. 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-transfer-management |
| description | Use when an agent needs to be transferred between teams. Trigger with transfer requests, transfer approvals, or transfer status checks. Loaded by ai-maestro-chief-of-staff-main-agent |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | AI Maestro v0.26.0+ |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Transfer management handles agent movement between teams using the GovernanceRequest API. Transfers require dual-manager approval: both source and target managers must approve before the agent is moved.
This skill is TEAM-SCOPED: you can only initiate transfers OUT of your team and accept transfers INTO your team.
State Machine: pending -> source-approved -> target-approved -> executed (rejection at any stage moves to rejected)
$AIMAESTRO_APIagent-messaging skill and amp-send.sh availableaimaestro-governance.sh request --type agent-transfer (the generic governance-request path; auth resolved internally)Copy this checklist and track your progress:
| Operation | Expected Output |
|---|---|
| Create TransferRequest | JSON with id, state: "pending" |
| Approve (source side) | State transitions to source-approved |
| Approve (target side) | State transitions to target-approved |
| Execute transfer | State transitions to executed |
| Reject transfer | State transitions to rejected |
| Error | Cause | Recovery |
|---|---|---|
404 on create | Agent/team ID not found | Verify IDs via registry |
409 on create | Pending transfer exists | Wait for existing to complete |
403 on approve | Not authorized approver | Verify your role matches |
409 on approve | Already in terminal state | No action needed |
| AMP delivery failure | Agent offline | Retry 3x with 10s intervals |
| Manager unresponsive | Approval pending | Remind after 30min, escalate after 2h |
Input: Transfer agent libs-svg-renderer from team libs-svg to team apps-editor
aimaestro-governance.sh request --type agent-transfer \
--payload-json '{"operation":"agent-transfer","agent":"libs-svg-renderer","sourceTeam":"libs-svg","targetTeam":"apps-editor"}'
Expected result: {"requestId": "tr-0017", "state": "pending"} then after dual approval: {"state": "executed"}
Version: 1.0.0 Last Updated: 2026-02-27