From emasoft-assistant-manager-agent
Use when coordinating with the Chief of Staff (ECOS) for approval requests and autonomous operation delegation. Trigger with ECOS coordination requests.
npx claudepluginhub emasoft/emasoft-plugins --plugin emasoft-assistant-manager-agentThis skill uses the workspace's default tool permissions.
This skill enables the Assistant Manager (EAMA) to coordinate with the Chief of Staff (ECOS) component. ECOS acts as the operational coordinator that can either request approval for operations or operate autonomously within granted boundaries.
references/ai-maestro-message-templates.mdreferences/approval-response-workflow.mdreferences/completion-notifications.mdreferences/creating-ecos-instance.mdreferences/creating-ecos-procedure.mdreferences/delegation-rules.mdreferences/examples.mdreferences/message-formats.mdreferences/spawn-failure-recovery.mdreferences/success-criteria.mdreferences/workflow-checklists.mdreferences/workflow-examples.mdProvides JSON templates for inter-agent messaging in AI Maestro, for task assignment, status reports, approvals, and escalations. Triggered by coordination needs.
Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.
Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.
Share bugs, ideas, or general feedback.
This skill enables the Assistant Manager (EAMA) to coordinate with the Chief of Staff (ECOS) component. ECOS acts as the operational coordinator that can either request approval for operations or operate autonomously within granted boundaries.
Before using this skill, ensure:
Copy this checklist and track your progress:
| Operation | Output |
|---|---|
| Create ECOS | ECOS agent spawned, registered |
| Grant autonomy | Autonomy scope confirmed |
| Revoke autonomy | Autonomy revoked, ECOS notified |
ECOS (Emasoft Chief of Staff) is a coordination component that manages day-to-day operational tasks. It sits between EAMA and the specialized roles (Architect, Orchestrator, Integrator).
USER
|
EAMA (Assistant Manager) - User's direct interface
|
ECOS (Chief of Staff) - Operational coordinator
|
+-- EAA (Architect)
+-- EOA (Orchestrator)
+-- EIA (Integrator)
| Component | Responsibilities |
|---|---|
| EAMA | User communication, final approvals, high-level decisions |
| ECOS | Task coordination, routine operations, delegation management |
EAMA is the ONLY agent authorized to create ECOS, ensuring single point of authority and role constraint enforcement.
See creating-ecos-instance.md:
ECOS sends approval requests to EAMA when:
| Category | Description | Default: Requires EAMA Approval |
|---|---|---|
critical-operation | Production deployments, database migrations | Always |
policy-exception | Deviation from standard procedures | Always |
resource-allocation | Budget, infrastructure, timeline changes | Always |
conflict-resolution | Inter-role disagreements | Always |
routine-operation | Standard development tasks | Delegatable |
minor-decision | Low-impact choices | Delegatable |
EAMA responds with: approved, rejected, or needs-revision. The response includes request_id, decision, optional comment, and conditions.
See approval-response-workflow.md:
Autonomous mode allows ECOS to proceed with certain operation types without requesting approval for each one. EAMA controls delegation via grant/revoke messages.
See delegation-rules.md:
All ECOS coordination happens via AI Maestro messages with specific JSON formats.
See message-formats.md:
ECOS notifies EAMA when operations complete. User notification depends on operation type and user preferences.
See completion-notifications.md:
| Error | Symptom | Solution |
|---|---|---|
| ECOS not found | No response to messages | Verify ECOS session exists, create if needed |
| Message send failure | AI Maestro API error | Check AI Maestro service status |
| Invalid approval format | ECOS rejects response | Review message format in Section 4 |
| Autonomy grant failed | ECOS doesn't acknowledge grant | Verify ECOS has latest plugin version |
| Duplicate request ID | Request ID collision | Use unique UUID for each request |
| Error | Cause | EAMA Action |
|---|---|---|
| ECOS unresponsive | ECOS session crashed or network issue | Alert user, attempt restart |
| Request timeout | EAMA took too long to respond | Auto-escalate to user |
| Invalid request format | Malformed message from ECOS | Return error, request retry |
| Scope exceeded | ECOS attempted unauthorized operation | Revoke autonomy, alert user |
| Conflicting requests | Multiple requests for same resource | Queue and resolve sequentially |
EAMA escalates to user when:
All ECOS interactions are logged:
ecos_audit_log:
- timestamp: "ISO-8601"
event_type: "request|response|grant|revoke|complete"
request_id: "ecos-req-{uuid}"
details: "Event description"
user_involved: true|false
For complete examples of ECOS coordination flows, see examples.md:
All messages sent to ECOS require acknowledgment (ACK) to ensure reliable communication. Different message types have different ACK timeout requirements.
| Message Type | ACK Timeout | Retry Behavior | Escalation |
|---|---|---|---|
| Approval decisions | 30 seconds | Retry once after timeout | Escalate to user if no ACK after retry |
| Work requests | 60 seconds | Retry once after timeout | Escalate to user if no ACK after retry |
| Health check pings | 60 seconds | No retry | Log as unresponsive |
| Status queries | 30 seconds | Retry once after timeout | Report timeout to user |
| Autonomy grant/revoke | 30 seconds | Retry once after timeout | Escalate to user if no ACK after retry |
ECOS must respond with an ACK message within the timeout period. The ACK message arrives via the agent-messaging skill with the following structure:
ecos-<project-name>normaltype: ackoriginal_message_id: The message ID of the original message being acknowledgedstatus: One of received (message received), processing (actively working on it), or completed (action done)timestamp: ISO-8601 timestamp of the acknowledgmentStep 1: Wait for Timeout
Step 2: Retry Once
Resend the original message with a retry flag using the agent-messaging skill:
ecos-<project-name>retry_of (original message ID) and retry_count (1)highVerify: confirm message delivery via the skill's sent messages feature.
Step 3: Escalate if Still No ACK If no ACK after retry:
docs_dev/sessions/ack-failures.mdECOS Communication Failure
Message: <subject>
Sent: <timestamp>
Retry: <retry-timestamp>
Status: No acknowledgment received
ECOS may be unresponsive. Options:
- [Check ECOS Health] - Send health ping
- [Retry Again] - Send message again
- [Respawn ECOS] - Terminate and recreate ECOS session
/eama-respond-to-ecos - Respond to pending ECOS approval requests/eama-configure-ecos-delegation - Configure ECOS delegation rules/eama-orchestration-status - View status including ECOS operationsRelated Skills:
eama-approval-workflows - General approval workflow patternseama-role-routing - Role routing and handoff patternsRelated Documentation: