القائمة
Use when running Plan-then-Execute workflows. Trigger with plan-execute or two-phase requests. Loaded by ai-maestro-orchestrator-agent-main-agent
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when sending inter-agent messages. Trigger with task assignment, status report, or escalation needs. Loaded by ai-maestro-orchestrator-agent-main-agent
Use when managing modules during Orchestration Phase. Trigger with module add, modify, or reassign requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Use when breaking down tasks for human developers. Trigger with task decomposition requests. Loaded by ai-maestro-orchestrator-agent-main-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
Use when verifying implementations. Trigger with verification, testing, or evidence requests. Loaded by ai-maestro-orchestrator-agent-main-agent
Use when running orchestration phase commands. Trigger with start, monitor, or cancel orchestration requests. Loaded by ai-maestro-orchestrator-agent-main-agent
| 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 |
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.