amoa-two-phase-mode

name	amoa-two-phase-mode
description	Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent
license	Apache-2.0
compatibility	AI Maestro, GitHub CLI (gh), remote agents.
metadata	{"author":"Emasoft","version":"2.6.0"}
context	fork
user-invocable	false
agent	amoa-main

Two-Phase Mode Skill

Overview

Plan Phase then Orchestration Phase. Stop hook enforces completion. For Plan Phase details, see skill amoa-plan-phase.

Prerequisites

AI Maestro messaging, GitHub CLI (gh), remote agents registered.

Instructions

1. /start-planning -- create state file, document requirements (see amoa-plan-phase)
2. /approve-plan -- transition to Orchestration Phase, create GitHub Issues
3. Register agents, assign modules, run Verification Protocol
4. /check-agents every 10-15 min; 4 verification loops per module

Copy this checklist and track your progress:

• /start-planning -- state file + requirements
• /approve-plan -- create Issues, start orchestration
• Assign modules, verify agents, monitor progress

Details: skill-overview-details.md

Examples

Input: /start-planning -- Output: Creates design/plan-state.yaml, enters Plan Phase. Input: /approve-plan -- Output: Creates GitHub Issues per module, starts Orchestration Phase.

Output

State YAML, GitHub Issues, phase confirmations. See state-file-formats.md.

Error Handling

See troubleshooting.md.

Resources

• skill-overview-details.md
• orchestration-phase-workflow.md
• instruction-verification-protocol.md
• state-file-formats.md
• troubleshooting.md