eoa-agent-replacement

Replace failed agents and transfer context via handoff documents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Emasoft/emasoft-orchestrator-agent --skill eoa-agent-replacement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eoa-agent-replacement
Source: https://github.com/Emasoft/emasoft-orchestrator-agent/tree/main/skills/eoa-agent-replacement
Command: npx skills add https://github.com/Emasoft/emasoft-orchestrator-agent --skill eoa-agent-replacement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Replacing a failed or unavailable agent without losing context or disrupting ongoing work.

Core Features & Use Cases

  • Handoff generation: Compile the failed agent's context and generate a complete handoff for the replacement agent.
  • Kanban reassignment: Reassign GitHub Project cards and project state to the new agent while preserving progress and metadata.
  • Handoff delivery & ACK: Deliver the handoff to the replacement agent via AI Maestro and require an acknowledgment with a readable understanding and continuation point.
  • ECOS integration & auditing: Notify ECOS about the replacement status and log outcomes for traceability.

Quick Start

Use the eoa-agent-replacement skill when ECOS notifies you of an agent failure to generate a replacement handoff, reassign tasks, and initiate handoff delivery. The commands used here are illustrative placeholders to demonstrate the flow and not a runnable script in this context.

Frequently Asked Questions about eoa-agent-replacement

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

FAQPage Schema
How do I automate agent replacement and handoff when an AI orchestrator agent fails?

Agent replacement and handoff is automated by compiling the failed agent's context, generating a handoff document, reassigning GitHub Kanban tasks, and delivering the package via AI Maestro. This ensures the replacement agent receives full context without disrupting ongoing work.

How do I reassign GitHub Project Kanban cards to a replacement AI agent?

GitHub Project Kanban cards are reassigned by transferring the failed agent's project state and metadata to the new agent. This preserves all task progress and card assignments while updating the orchestrator state to reflect the replacement agent's ownership.

What is an agent handoff document and when do I need to generate one?

An agent handoff document is a compiled record of a failed or unavailable agent's context, progress, and continuation point. You need to generate one when an agent failure requires a successor to take over tasks without losing prior context or disrupting workflows.

Do I need Python and GitHub CLI to perform automated agent context handoffs?

Yes, automated agent context handoffs require Python 3.8+ with PyYAML and the GitHub CLI installed. You also need access to the orchestrator's state and GitHub project data to compile context and reassign tasks properly.

What happens after handoff delivery to the replacement agent via AI Maestro?

After handoff delivery via AI Maestro, the replacement agent must send an acknowledgment confirming its understanding of the context and continuation point. The system then notifies ECOS about the replacement status and logs the outcome for traceability and auditing.

Can I trigger an emergency agent replacement instead of a standard handoff?

Yes, the system supports both standard and emergency agent replacements. Emergency workflows follow the same context compilation and handoff delivery steps but prioritize immediate task reassignment and ECOS notification to minimize workflow disruption.