メニュー
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
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 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 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
| name | amcos-emergency-handoff |
| description | 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 |
| user-invocable | false |
| license | Apache-2.0 |
| compatibility | Requires AI Maestro installed. |
| metadata | {"author":"Emasoft","version":"1.0.0"} |
| context | fork |
| agent | ai-maestro-chief-of-staff-main-agent |
Transfer critical work when deadlines cannot wait. Routes task blocker escalations to AMAMA.
$CLAUDE_PROJECT_DIR/thoughts/shared/handoffs/emergency/| Aspect | Regular | Emergency |
|---|---|---|
| Timing | After replacement | Immediately |
| Completeness | Full context | Minimum viable |
| Recipient | Replacement | Any available |
| Duration | Permanent | Temporary |
Agent Failures -- resolve via failure recovery workflow.
Task Blockers -- blocked by missing info/access/user decision:
blocker-escalationEscalation -> Agent failure? -> recovery workflow
-> Blocker AMCOS resolves? -> handle
-> Needs user input? -> route to AMAMA
Copy this checklist and track your progress:
| Result | Output |
|---|---|
| Handoff sent | Work transferred to available agent |
| Blocker routed | Awaiting AMAMA user decision |
| Blocker resolved | Agent reassigned directly |
| Issue | Resolution |
|---|---|
| No available agent | Notify AMAMA for manual intervention |
| Handoff rejected | Try next available agent |
| Deadline missed | Document, notify, post-mortem |
| AMAMA unresponsive | 15 min wait, reminder, escalate |
amp-send.sh apps-svgplayer-development "EMERGENCY: SVG fix (2h)" urgent \
'{"type":"emergency-handoff","message":"svgbbox crashed. Fix by 18:00 UTC.","task":"Fix SVG rendering","failed_agent":"libs-svg-svgbbox","deadline":"2025-02-05T18:00:00Z"}'
amp-send.sh amama-assistant-manager "BLOCKER: API key needed" high \
'{"type":"blocker-escalation","message":"API key needed, user must provide.","blocker_type":"user-decision","impact":"Deploy blocked","escalated_from":"amoa-deployment"}'
Copy this checklist and track your progress: