Help us improve
Share bugs, ideas, or general feedback.
From ai-maestro-assistant-manager-agent
Use when coordinating with COS for approvals and delegation. Trigger with COS coordination requests. Loaded by ai-maestro-assistant-manager-agent-main-agent
npx claudepluginhub emasoft/ai-maestro-assistant-manager-agentHow this skill is triggered — by the user, by Claude, or both
Slash command
/ai-maestro-assistant-manager-agent:amama-amcos-coordinationamama-assistant-manager-main-agentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Coordinates with COS-assigned agents. See [cos-definition](references/cos-definition.md).
references/ack-protocol.mdreferences/ai-maestro-message-templates.mdreferences/approval-request-flow.mdreferences/approval-response-workflow.mdreferences/completion-notifications.mdreferences/cos-definition.mdreferences/creating-amcos-instance.mdreferences/creating-amcos-procedure.mdreferences/delegation-rules.mdreferences/error-handling.mdreferences/examples.mdreferences/message-formats.mdreferences/spawn-failure-recovery.mdreferences/success-criteria.mdreferences/workflow-checklists.mdreferences/workflow-examples.mdCreates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Coordinates with COS-assigned agents. See cos-definition.
GET /api/agents)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
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
When AMCOS Sends Completion Notifications · Processing Completion Notifications · User Notification Rules
Checklist: identify op type → verify agent registered → execute API call → await ACK (30-60s).
| 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 |
See references/error-handling.md. Escalate on: decision failure, critical failure, security concern, or timeout.
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.
AMCOS Approval Request Format · AMAMA Response Format · Autonomy Messages · Completion Notification Format
Receiving Messages · Sending Approval-Related Messages · Requesting Information from AMCOS · Delegating Work to AMCOS · Standard AI Maestro Messaging Patterns
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
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