amoa-two-phase-mode

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

7 stars

Best use case

amoa-two-phase-mode is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Teams using amoa-two-phase-mode should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/amoa-two-phase-mode/SKILL.md --create-dirs "https://raw.githubusercontent.com/Emasoft/ai-maestro-orchestrator-agent/main/skills/amoa-two-phase-mode/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/amoa-two-phase-mode/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How amoa-two-phase-mode Compares

Feature / Agentamoa-two-phase-modeStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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](references/skill-overview-details.md)
<!-- TOC: Output Types and Locations | Step-by-Step Instructions | Agent Types | Stop Hook Enforcement | File Structure | Examples -->

## 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](references/state-file-formats.md).
<!-- TOC: Plan Phase State File | 1 File location | 2 Complete YAML schema | 3 Field descriptions | Orchestration Phase State File | 1 File location | 2 Complete YAML schema | 3 Field descriptions | Agent Assignment Structure | 1 Assignment fields | 2 Instruction verification tracking | 3 Progress polling tracking | Module Status Structure | 1 Module fields | 2 Status values -->

## Error Handling

See [troubleshooting.md](references/troubleshooting.md).
<!-- TOC: Two-Phase Mode Troubleshooting | Contents | 1. Plan Phase Issues | 2. Orchestration Phase Issues | 3. State File Issues | 4. Communication Issues | 5. Stop Hook Issues | Related References -->

## Resources

- [skill-overview-details.md](references/skill-overview-details.md)
- [orchestration-phase-workflow.md](references/orchestration-phase-workflow.md)
- [instruction-verification-protocol.md](references/instruction-verification-protocol.md)
- [state-file-formats.md](references/state-file-formats.md)
- [troubleshooting.md](references/troubleshooting.md)

Related Skills

amoa-verification-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-task-distribution

7
from Emasoft/ai-maestro-orchestrator-agent

Use when distributing tasks. Trigger with task assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-remote-agent-coordinator

7
from Emasoft/ai-maestro-orchestrator-agent

Use when coordinating remote AI agents via AI Maestro messaging. NOT for human coordination. Trigger with agent delegation or multi-agent requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-progress-monitoring

7
from Emasoft/ai-maestro-orchestrator-agent

Use when monitoring agent progress. Trigger with status check or stall detection requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-plan-phase

7
from Emasoft/ai-maestro-orchestrator-agent

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

amoa-orchestration-patterns

7
from Emasoft/ai-maestro-orchestrator-agent

Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-orchestration-loop

7
from Emasoft/ai-maestro-orchestrator-agent

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

amoa-module-sync

7
from Emasoft/ai-maestro-orchestrator-agent

Use when syncing modules with GitHub Issues or troubleshooting module state. Trigger with sync, issue, or module troubleshooting requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-management

7
from Emasoft/ai-maestro-orchestrator-agent

Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-module-lifecycle

7
from Emasoft/ai-maestro-orchestrator-agent

Use when adding, modifying, removing, prioritizing, or reassigning modules. Trigger with module CRUD requests. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-messaging-templates

7
from Emasoft/ai-maestro-orchestrator-agent

Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent

amoa-label-taxonomy

7
from Emasoft/ai-maestro-orchestrator-agent

Use when applying GitHub labels. Trigger with label query or assignment requests. Loaded by ai-maestro-orchestrator-agent-main-agent