amoa-agent-replacement

Use when replacing agents. Trigger with agent replacement or handoff requests. Loaded by ai-maestro-orchestrator-agent-main-agent

7 stars

Best use case

amoa-agent-replacement is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when replacing agents. Trigger with agent replacement or handoff requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Teams using amoa-agent-replacement should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amoa-agent-replacement/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-agent-replacement/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amoa-agent-replacement/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amoa-agent-replacement Compares

Feature / Agentamoa-agent-replacementStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when replacing agents. Trigger with agent replacement or handoff requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Agent Replacement Skill

## Overview

Handle agent replacement triggered by AMCOS. When an agent fails or loses context, compile task context and generate handoff documents for the replacement.


## Prerequisites

Python 3.8+, PyYAML, GitHub CLI (gh) authenticated, AI Maestro running, AMCOS operational.

## Output

Handoff document (GitHub issue comment), state file update, AMCOS confirmation, kanban reassignment.

## Instructions

1. On AMCOS notification, compile task context from the failed agent's GitHub issues, kanban cards, and AI Maestro message history.
2. Generate a handoff document and deliver it to the replacement agent via AI Maestro `agent-messaging` skill.
3. Wait for ACK, confirm reassignment, and notify AMCOS of successful replacement.

See: [replacement-workflow-steps.md](references/replacement-workflow-steps.md) for detailed steps.
<!-- TOC: Replacement Protocol Flow | Step 1: Receive AMCOS Notification | Step 2: Compile Task Context | Step 3: Generate Handoff Document | Step 4: Reassign Kanban Tasks | Step 5: Send Handoff to New Agent | Step 6: Confirm Reassignment | Python Scripts -->

## Checklist

Copy this checklist and track your progress:

- [ ] Receive and acknowledge AMCOS replacement notification
- [ ] Compile all task context from failed agent
- [ ] Generate comprehensive handoff document
- [ ] Reassign GitHub Project kanban tasks
- [ ] Send handoff to new agent via AI Maestro `agent-messaging` skill
- [ ] Confirm ACK receipt and requirements understanding
- [ ] Update orchestrator state file
- [ ] Notify AMCOS of successful replacement

## Examples

**Input:** AMCOS notification `{"type": "agent-failed", "agent": "libs-svg-svgbbox", "reason": "context-loss"}`
**Output:** Handoff document posted to GitHub issue + kanban tasks reassigned + AMCOS confirmation sent

See: [examples.md](references/examples.md) for full examples.
<!-- TOC: Example 1: Standard Replacement Flow | Example 2: Emergency Replacement with Partial Context -->

## Error Handling

See: [error-handling-reference.md](references/error-handling-reference.md) for errors and solutions.
<!-- TOC: Common Errors and Solutions | Troubleshooting References | Emergency Procedures -->

## Resources

- [replacement-workflow-steps.md](references/replacement-workflow-steps.md) - 6-step workflow
  - 1. Replacement Protocol Flow
  - 2. Step 1: Receive AMCOS Notification
  - 3. Step 2: Compile Task Context
  - 4. Step 3: Generate Handoff Document
  - 5. Step 4: Reassign Kanban Tasks
  - ...
- [error-handling-reference.md](references/error-handling-reference.md) - Errors
  - 1. Common Errors and Solutions
  - 2. Troubleshooting References
  - 3. Emergency Procedures
- [handoff-document-format.md](references/handoff-document-format.md) - Handoff format
  - 3.1 Required Sections
    - Mandatory Sections
    - Section Order
  - Template
  - Handoff Metadata
  - ...
- [examples.md](references/examples.md) - Examples
  - Example 1: Standard Replacement Flow
  - Example 2: Emergency Replacement with Partial Context
- [emergency-procedures.md](references/emergency-procedures.md) - Emergencies
  - Replacement Agent Also Fails
  - Handoff Document Corrupted
  - GitHub Project Access Issues
- [context-compilation-workflow.md](references/context-compilation-workflow.md) - Context gathering
  - 2.1 Information Sources
    - Primary Sources (MUST check)
    - Secondary Sources (SHOULD check)
    - Tertiary Sources (MAY check)
  - 2.2 State File Extraction
  - ...

Related Skills

amoa-verification-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-two-phase-mode

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-task-distribution

7
from Emasoft/ai-maestro-orchestrator-agent

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-remote-agent-coordinator

7
from Emasoft/ai-maestro-orchestrator-agent

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-progress-monitoring

7
from Emasoft/ai-maestro-orchestrator-agent

Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-plan-phase

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running Plan Phase of two-phase mode. Trigger with planning, requirements, or plan approval requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-loop

7
from Emasoft/ai-maestro-orchestrator-agent

Use when running the orchestrator loop or managing stop hook behavior. Trigger with loop, stop hook, or state file requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-sync

7
from Emasoft/ai-maestro-orchestrator-agent

Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-management

7
from Emasoft/ai-maestro-orchestrator-agent

Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-lifecycle

7
from Emasoft/ai-maestro-orchestrator-agent

Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-messaging-templates

7
from Emasoft/ai-maestro-orchestrator-agent

Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent