amcos-emergency-handoff

Transfer critical work to an available agent during failures or blockers.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-emergency-handoff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amcos-emergency-handoff
Source: https://github.com/Emasoft/ai-maestro-chief-of-staff/tree/main/skills/amcos-emergency-handoff
Command: npx skills add https://github.com/Emasoft/ai-maestro-chief-of-staff --skill amcos-emergency-handoff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables immediate emergency handoffs when an agent fails or a task blocker threatens deadlines, ensuring critical work continues without delay.

Core Features & Use Cases

  • Identify critical tasks affected by a failure or blocker and initiate a minimal handoff process.
  • Notify the orchestrator (EOA) and manager (EAMA), generate handoff documentation, reassign to an available receiving agent, and monitor progress until resolution.
  • Differentiate emergency handoff from regular replacement by prioritizing urgent reallocation and reconciliation while preserving incident context.

Quick Start

Initiate an emergency handoff whenever a deadline-critical failure is detected to reassign work to an available agent and notify the appropriate stakeholders.

Frequently Asked Questions about amcos-emergency-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle an emergency handoff when an agent fails and threatens a deadline?

An emergency handoff immediately transfers critical work when an agent fails. It identifies affected tasks, generates minimal handoff documentation, reassigns work to an available agent, and monitors progress to minimize downtime.

What is the difference between an emergency handoff and regular task replacement?

An emergency handoff prioritizes urgent reallocation and reconciliation while preserving incident context, whereas regular replacement does not enforce emergency-first decision logic or capture artifacts specifically for post-mortem and incident tracking.

How does incident management orchestration coordinate task reallocation across agents?

Incident management orchestration coordinates with AMCOS, EOA, and EAMA to identify critical tasks, generate handoff documents, reassign them to available receiving agents, and monitor progress through completion while logging events for tracking.

When do I need to initiate an emergency handoff for task blockers?

You need to initiate an emergency handoff whenever a deadline-critical failure or task blocker is detected. This triggers immediate work reassignment to an available agent and notifies appropriate stakeholders to ensure resolution.

Does the emergency handoff process capture artifacts for post-mortem analysis?

Yes, the emergency handoff process captures artifacts for post-mortem analysis and logs events for incident tracking. This ensures full incident context is preserved while coordinating urgent reallocation across AMCOS, EOA, and EAMA systems.

Can I use this emergency handling process without dependencies?

Yes, you can use this emergency handling process without dependencies. It operates independently to identify critical tasks, generate handoff documentation, and reassign work to available receiving agents when deadline-threatening failures occur.