Stats
Actions
Tags
From ai-maestro-orchestrator-agent
Manages AI Maestro orchestrator loop lifecycle, stop hooks, and state files. Monitors tasks from Claude Tasks, GitHub Projects, files; enforces 4-loop verification before completion.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ai-maestro-orchestrator-agent:amoa-orchestration-loopamoa-mainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Manages the orchestrator loop lifecycle, stop hook behavior, and state files during orchestration.
Manages the orchestrator loop lifecycle, stop hook behavior, and state files during orchestration.
Orchestration Phase active, state file design/state/exec-phase.md exists.
Loop state reports, stop hook blocking reasons, state file updates.
/orchestrator-loop for continuous task processingALL_TASKS_COMPLETECopy this checklist and track your progress:
/orchestrator-loop/orchestration-status every 10-15 min/cancel-orchestrator when completeSee orchestration-loop-mechanics.md
Input: /orchestrator-loop "Complete auth tasks" --max-iterations 50
Output: Continuous processing started, monitoring all task sources.
More: examples.md
See reference files above for complete details on loop mechanics, state files, and troubleshooting.
npx claudepluginhub emasoft/ai-maestro-orchestrator-agentRuns orchestration commands to coordinate agents executing approved plans. Use after plan approval to start, monitor, or cancel orchestration phases with status tracking.
Manages Maestro orchestration session state: creation, updates, tracking, resumption, and archiving via MCP tools, file edits, or scripts.
Orchestrates multi-agent workflows with parallel pipelines, sync barriers, state tracking, checkpointing, and progress metrics. Use for coordinating 3+ agents across sessions.