amama-amcos-coordination

COS Coordination Skill

Overview

Coordinates with COS-assigned agents. See cos-definition.

Prerequisites

1. Target agent in AI Maestro registry (GET /api/agents)
2. AI Maestro messaging available
3. A team exists or will be created

Instructions

1. Recommend COS — Suggest agents for COS role. USER assigns via dashboard. See creating-amcos-instance.

   Why AMAMA Assigns the COS Role · How to Assign the COS Role · When to Assign the COS Role · Post-Assignment Steps · Cross-Host COS Assignment

2. Register Agents — POST /api/agents/register. See creating-amcos-procedure.

   Overview · Key Principles · Agent Registration · Team Creation · COS Assignment · Step-by-Step Procedure · Success Criteria · Troubleshooting · Related Documents

3. Approvals — Evaluate, respond. See references/approval-request-flow.md.

• When COS-Assigned Agent Sends Approval Requests
• Request Categories
• Related Documents

4. Respond — Send decision. See references/approval-response-workflow.md.

• Decision Options
• When to Use Each Decision
• Response Format
• Field Descriptions
• Response Workflow

5. Delegation — Grant/revoke autonomy. See references/delegation-rules.md.

• What is Autonomous Mode
• Delegation Configuration
• Granting Autonomous Mode
• Grant Parameters
• Revoking Autonomous Mode
• Revocation Message
• Revocation Reasons
• Operations That ALWAYS Require AMAMA Approval

6. Completions — Handle notifications. See completion-notifications.

   When AMCOS Sends Completion Notifications · Processing Completion Notifications · User Notification Rules

7. ACK — Require ACK 30-60s. See references/ack-protocol.md.

• ACK Timeout Requirements
• ACK Message Format
• Handling Missing ACK
• ACK Verification Checklist

Checklist: identify op type → verify agent registered → execute API call → await ACK (30-60s).

Output

Operation	Output
Recommend COS	COS candidate recommended to user
Request team	Team creation request sent
Grant autonomy	Scope confirmed by COS
Revoke autonomy	COS agent notified

Error Handling

See references/error-handling.md. Escalate on: decision failure, critical failure, security concern, or timeout.

Examples

Input: User assigns COS via dashboard for team-1 with agent amcos-cos

Output: AMAMA verifies assignment: GET /api/teams/team-1 returns {"chiefOfStaff":"amcos-cos","status":"assigned"}

See references/workflow-examples.md for full examples.

• Example 1: User Requests New Project
• Example 2: AMCOS Requests Approval (Low Risk)
• Example 3: AMCOS Requests Approval (High Risk)
• Example 4: User Requests Status
• Example 5: COS Role Assignment Failure
• COS Role Assignment Failure Recovery Protocol
• Handoff Pattern

Resources

• references/message-formats.md - JSON formats

  AMCOS Approval Request Format · AMAMA Response Format · Autonomy Messages · Completion Notification Format

• ai-maestro-message-templates - Templates

  Receiving Messages · Sending Approval-Related Messages · Requesting Information from AMCOS · Delegating Work to AMCOS · Standard AI Maestro Messaging Patterns

• success-criteria - Success criteria

  Success: User Request Understood · Success: Project and Team Creation Complete · Success: AMCOS Agent Created and Ready · Success: Approval Processed · Success: Status Reported · General Success Verification Principles

• references/workflow-checklists.md - Checklists
  • Checklist: Creating New Team
  • Checklist: Assigning COS Role
  • Checklist: Processing AMCOS Approval Request
  • Checklist: Routing User Request to AMCOS
  • Checklist: Providing Status to User
• spawn-failure-recovery - Recovery

  Overview · AMCOS COS Assignment Failure Recovery Protocol · Communication Breakdown Recovery · Approval Request Handling Failures · Agent Creation Failures (General) · Logging and Audit Trail · Timeliness Requirements · Example Scenarios · Summary