amoa-orchestration-loop

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

7 stars

Best use case

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

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

Teams using amoa-orchestration-loop 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-orchestration-loop/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-orchestration-loop/SKILL.md"

Manual Installation

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

How amoa-orchestration-loop Compares

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

Frequently Asked Questions

What does this skill do?

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

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

# Orchestration Loop Skill

## Overview

Manages the orchestrator loop lifecycle, stop hook behavior, and state files during orchestration.

## Prerequisites

Orchestration Phase active, state file `design/state/exec-phase.md` exists.

## Output

Loop state reports, stop hook blocking reasons, state file updates.

## Instructions

1. Start loop with `/orchestrator-loop` for continuous task processing
2. Loop monitors task sources (Claude Tasks, GitHub Projects, task files, TODO list)
3. Uses 4-loop verification before allowing completion
4. Stop hook blocks exit when tasks pending; signal `ALL_TASKS_COMPLETE`

Copy this checklist and track your progress:

- [ ] Start loop with `/orchestrator-loop`
- [ ] Monitor via `/orchestration-status` every 10-15 min
- [ ] Cancel with `/cancel-orchestrator` when complete

See [orchestration-loop-mechanics.md](references/orchestration-loop-mechanics.md)
<!-- TOC: 1 What the orchestrator loop does | 2 Task source monitoring and priority | 3 Iteration counting and max iterations | 4 Verification mode (4-loop quadruple-check) | 5 Completion signals (ALL_TASKS_COMPLETE) | 6 Stop hook behavior and blocking logic -->

See [stop-hook-behavior.md](references/stop-hook-behavior.md)
<!-- TOC: Blocking conditions - When the stop hook prevents exit | Completion signals - How to signal task completion | Recovery behavior - Fail-safe and retry logic -->

See [state-file-format.md](references/state-file-format.md)
<!-- TOC: 1 Loop state file format and fields | 2 Execution phase state file format | 3 Frontmatter field definitions | 4 How to manually edit state files | 5 State file corruption recovery -->

## Examples

**Input:** `/orchestrator-loop "Complete auth tasks" --max-iterations 50`
**Output:** Continuous processing started, monitoring all task sources.

More: [examples.md](references/examples.md)
<!-- TOC: Complete Orchestration Start - Full startup workflow | Orchestrator Loop Usage - Loop start, status, cancel | Monitoring During Implementation - Agent checking workflow -->

## Error Handling

See [troubleshooting.md](references/troubleshooting.md)
<!-- TOC: 1 Loop won't start - common causes | 2 Stop hook not firing - debugging steps | 3 Tasks showing as pending incorrectly | 4 Lock file issues and stale locks | 5 Concurrent execution conflicts | 6 Verification mode stuck | 7 Helper script failures | 8 Using /reload-plugins -->

## Resources

See reference files above for complete details on loop mechanics, state files, and troubleshooting.

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-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

amoa-label-taxonomy

7
from Emasoft/ai-maestro-orchestrator-agent

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent