amoa-agent-replacement

Generate replacement handoffs and reassign tasks for failed agents.

13|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-agent-replacement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amoa-agent-replacement
Source: https://github.com/Emasoft/ai-maestro-orchestrator-agent/tree/main/skills/amoa-agent-replacement
Command: npx skills add https://github.com/Emasoft/ai-maestro-orchestrator-agent --skill amoa-agent-replacement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When an agent fails, becomes unresponsive, or suffers context loss, this Skill centralizes and automates the recovery workflow so work continues with minimal disruption. It compiles all task context, generates structured handoff documents, reassigns GitHub Project kanban cards, delivers the handoff to replacement agents via AI Maestro, and confirms successful replacement with ACK verification and state updates.

Core Features & Use Cases

  • Compile context from orchestrator state files, GitHub issues, git branches, and AI Maestro message history to create a single continuity document.
  • Generate and upload handoff documents to GitHub, attach audit comments, and provide local backups for persistence.
  • Reassign project board cards and issue labels while preserving status, add reassignment audit comments, and update orchestrator state YAML.
  • Deliver handoffs via AI Maestro agent-messaging, require and validate ACKs, retry or escalate on timeouts, and log audit records for compliance.
  • Use cases: AMCOS immediate replacement, pre-emptive context-limit handoffs, emergency partial-context recovery, and automated reassignment after agent timeouts.

Quick Start

Instruct the orchestrator to generate a replacement handoff for failed agent implementer-1, reassign their GitHub Project cards to implementer-2, deliver the handoff via AI Maestro, and await ACK.

Frequently Asked Questions about amoa-agent-replacement

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

FAQPage Schema
How do I automate agent handoffs when an AI agent crashes or loses context?

Automated agent handoffs compile orchestrator state, GitHub issues, git branches, and AI Maestro message history into a continuity document. The system generates GitHub handoff comments, reassigns kanban project cards, and delivers the context to a replacement agent.

What is the best way to reassign GitHub Project kanban cards after an agent timeout?

Reassigning GitHub Project kanban cards after a timeout involves updating issue labels, preserving task status, adding reassignment audit comments, and modifying orchestrator state YAML. This ensures the replacement agent receives accurate project board tracking.

Can I use AI Maestro to deliver replacement handoffs and verify agent ACKs?

Yes, handoffs are delivered via AI Maestro agent-messaging. The system requires and validates ACKs from the replacement agent, automatically retrying or escalating on timeouts while logging audit records for compliance and verification.

How does context compilation work for emergency partial-context recovery?

Context compilation for recovery extracts data from orchestrator state files, GitHub issues, git branches, and AI Maestro message history. This data generates a structured handoff document uploaded to GitHub with local backups for persistence.

Do I need an orchestrator state YAML file to generate a replacement handoff?

Yes, an orchestrator state YAML file is required to generate replacement handoffs. The system reads and updates this state file alongside GitHub issues and AI Maestro message history to ensure accurate task reassignment and continuity.