菜单
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
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | amcos-acknowledgment-protocol |
| description | 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 |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Requires access to AI Maestro messaging system. Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Ensures agents confirm readiness before disruptive operations via ACK requests, timeout management, reminders, and timeout handling.
amp-init.sh --autoWhen to use: When agent confirmation is needed before proceeding, or when coordinating multi-agent operations.
Workflow:
amp-send.sh to ask agent to reply "ok"Copy this checklist and track your progress:
See op-acknowledgment-protocol in Resources for full procedure details and examples.
CRITICAL: All AMCOS components MUST use these values:
| ACK Type | Timeout | Reminders | Use Case |
|---|---|---|---|
| Pre-operation ACK | 60s | 15s, 30s, 45s | Before disruptive ops |
| Approval request | 2 min | 60s, 90s | Manager approval |
| Emergency handoff | 30s | 10s, 20s | Time-critical emergencies |
| Health check | 30s | None | Verifying agent alive |
Timeout behavior: Pre-op ACK: proceed after final notice. Approval: proceed if autonomous, else abort. Emergency: proceed immediately.
| Action | Output |
|---|---|
| ACK request sent | Delivered, timeout timer started |
| ACK received | Agent confirmed, operation may proceed |
| Timeout reached | Final notice sent, logged, fallback taken |
| Issue | Resolution |
|---|---|
| ACK timeout | Send final notice, log, proceed per policy |
| Reminder not delivered | Health check agent. If offline, proceed per timeout |
| Partial ACK (multi-agent) | Track per-agent. Proceed when all respond or all timeout |
# Send ACK request before disruptive operation
amp-send.sh code-impl-auth "ACK: hibernate in 60s" high \
'{"type":"acknowledgment-request","timeout":60}'
Expected: agent replies "ok" within 60s; if no reply after reminders at 15s/30s/45s, proceed with final notice.
Copy this checklist and track your progress:
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 replacing a failed agent with a new instance. Trigger with agent replacement or failover events. Loaded by ai-maestro-chief-of-staff-main-agent
Use when handling emergency work handoff from failed agents. Trigger with agent failure handoff or task blocker routing. Loaded by ai-maestro-chief-of-staff-main-agent