amoa-plan-phase

name	amoa-plan-phase
description	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
license	Apache-2.0
compatibility	AI Maestro, GitHub CLI (gh), remote agents.
metadata	{"author":"Emasoft","version":"1.0.0"}
context	fork
user-invocable	false
agent	amoa-main

Plan Phase Skill

Overview

Plan Phase of two-phase mode: document requirements, decompose into modules, approve plan for execution.

Prerequisites

AI Maestro messaging, GitHub CLI (gh).

Instructions

Use native-task-persistence.md for Claude Tasks.

1. /start-planning -- create state file, document requirements
2. Add/modify/remove requirements as needed
3. /approve-plan -- transition to Orchestration Phase, create GitHub Issues

Copy this checklist and track your progress:

• /start-planning -- state file + requirements
• Document and refine requirements
• /approve-plan -- create Issues, start orchestration

Commands: command-reference.md

Output

State YAML, GitHub Issues, phase confirmations. See state-file-formats.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.

Error Handling

See troubleshooting.md.

Resources

• command-reference.md
• plan-phase-workflow.md
• state-file-formats.md
• troubleshooting.md