菜单
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
用 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 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
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
| name | amcos-failure-notification |
| description | 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 |
| 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 |
Failure notifications inform agents when operations fail, with error details, severity levels, and recovery guidance. Covers failure messaging, cascading failures, and proactive handoffs.
amp-init.sh --autoWhen to use: When any operation fails (skill install, restart, config change, timeout).
Workflow:
critical (system-wide), error (single op), warning (degraded)amp-send.sh exclusivelyCopy this checklist and track your progress:
amp-send.sh with recovery guidanceSee op-failure-notification — Topics: Failure Notification, Contents, When to Use, Prerequisites, Procedure, Step 1: Capture Error Details, Step 2: Compose Failure Message, Step 3: Send Failure Notification, Step 4: Provide Recovery Guidance, Step 5: Log Failure, Checklist, Examples, Example 1: Skill Installation Failure, Example 2: Agent Restart Failure, Example 3: Configuration Change Failure, Example 4: Timeout Failure Notification, Error Severity Levels, Error Handling, Related Operations
| Type | Output |
|---|---|
| Failure alert | Notification sent with error details and severity |
| Recovery guidance | Recovery steps provided to affected agents |
| Failure log | Error context recorded with timestamp |
| Issue | Resolution |
|---|---|
| Not delivered | Retry after 10s. If offline, queue. See references Section 4.8 |
| AI Maestro unavailable | Fallback per edge case protocols |
| Agent cannot recover | Escalate to MANAGER with full context |
| Cascading failure | Follow cascading protocol in edge case reference |
# Send failure notification after skill install error
amp-send.sh code-impl-auth "FAILURE: skill install" high \
'{"type":"failure","error":"Skill validation failed - missing SKILL.md","recovery":"Fix SKILL.md and retry"}'
Expected: agent receives failure details with recovery steps; failure logged with timestamp.
Copy this checklist and track your progress: