From ai-maestro-orchestrator-agent
Manages Plan-then-Execute workflows: /start-planning creates state YAML, /approve-plan generates GitHub Issues, assigns remote agents, runs verification loops. For AI Maestro orchestration.
npx claudepluginhub emasoft/ai-maestro-orchestrator-agentThis skill uses the workspace's default tool permissions.
Plan Phase then Orchestration Phase. Stop hook enforces completion. For Plan Phase details, see skill `amoa-plan-phase`.
README.mdreferences/command-reference.mdreferences/design-folder-structure-part1-overview.mdreferences/design-folder-structure-part2-file-types.mdreferences/design-folder-structure-part3-workflow.mdreferences/design-folder-structure-part4-multiplatform.mdreferences/design-folder-structure.mdreferences/instruction-update-verification-protocol-part1-core-protocol.mdreferences/instruction-update-verification-protocol-part2-special-cases.mdreferences/instruction-update-verification-protocol.mdreferences/instruction-verification-protocol.mdreferences/issue-handling-workflow.mdreferences/native-task-persistence.mdreferences/op-approve-plan-transition.mdreferences/op-create-github-issues.mdreferences/op-decompose-goals-to-modules.mdreferences/op-define-acceptance-criteria.mdreferences/op-prioritize-task-assignments.mdreferences/op-schedule-claude-tasks.mdreferences/orchestration-phase-workflow.mdHandles Plan Phase in AI Maestro two-phase mode: starts with /start-planning to document requirements, refines them, approves plan via /approve-plan creating GitHub Issues for modules.
Executes multi-phase implementation plans by dispatching task implementers and reviewers, tracking progress per task in plan.json. Use for independent tasks in sessions.
Executes approved Maestro implementation plans using shared session-state contract, coordinating tools like Agent, Bash, task management for complex workflows.
Share bugs, ideas, or general feedback.
Plan Phase then Orchestration Phase. Stop hook enforces completion. For Plan Phase details, see skill amoa-plan-phase.
AI Maestro messaging, GitHub CLI (gh), remote agents registered.
/start-planning -- create state file, document requirements (see amoa-plan-phase)/approve-plan -- transition to Orchestration Phase, create GitHub Issues/check-agents every 10-15 min; 4 verification loops per moduleCopy this checklist and track your progress:
/start-planning -- state file + requirements/approve-plan -- create Issues, start orchestrationDetails: skill-overview-details.md
Input: /start-planning -- Output: Creates design/plan-state.yaml, enters Plan Phase.
Input: /approve-plan -- Output: Creates GitHub Issues per module, starts Orchestration Phase.
State YAML, GitHub Issues, phase confirmations. See state-file-formats.md.
See troubleshooting.md.