amoa-orchestration-loop

name	amoa-orchestration-loop
description	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
license	Apache-2.0
compatibility	Python 3.8+, PyYAML, GitHub CLI, AI Maestro.
metadata	{"author":"Emasoft","version":"1.0.0"}
user-invocable	false
context	fork
agent	amoa-main

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

See stop-hook-behavior.md

See state-file-format.md

Examples

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

More: examples.md

Error Handling

See troubleshooting.md

Resources

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