ampa-orchestrator-communication

AMPA Orchestrator Communication Skill

Overview

Defines all communication protocols between AMPA and AMOA. Uses asynchronous inter-agent messaging via the globally installed agent-messaging skill. Read that skill once during initialization to learn messaging commands and syntax.

Prerequisites

• agent-messaging skill installed: Read it to learn send/receive/reply commands.
• AMOA session name known: Your assigned orchestrator must be active and registered.
• Messaging identity verified: Your session name is registered via agent-messaging initialization.

Instructions

Copy this checklist and track your progress:

1. Initialize: Read the agent-messaging skill and follow its initialization to register your messaging identity.
2. Verify connectivity: Use agent-messaging status check to confirm the service is running.
3. Identify operation type: Determine which applies — clarification, status, blocker, improvement, completion, or feedback acknowledgment.
4. Read reference file: Open the corresponding reference file from Resources below to learn the exact message format and required fields.
5. Compose message: Build the message with correct type, priority, subject, and structured content as specified in the reference.
6. Send message: Use agent-messaging send operation to deliver to AMOA. Retry up to 3 times on failure.
7. Verify delivery: Confirm the message appears in your sent messages list.
8. Monitor for response: Check inbox for AMOA replies. Process all unread messages before continuing other work.
9. Acknowledge receipt: Reply to AMOA confirming you received the response and stating your next action.

Output

Sent/received messages to/from AMOA via agent-messaging skill.

Error Handling

If message delivery fails after 3 retries, write the message content to docs_dev/unsent-<timestamp>.md and report the delivery failure to your local log. Resume when connectivity is restored.

Examples

• Input: Need to report progress on task #42
• Output: {"type": "status-update", "message": "Task #42: 3/5 criteria met. Details: docs_dev/status-42.md"}

Resources

Document	Description
op-comprehension-handshake.md	The task-comprehension handshake answer (all 5 points, before coding) — replaces the bare ACK (R6 v3 / #17 M7a)
op-request-clarification.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-report-status.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-report-blocker.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-propose-improvement.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-notify-completion.md	When to Use, Prerequisites, Procedure, Examples, Error Handling
op-pre-pr-gate.md	The "PR now?" pre-PR gate — ask AMOA for a green-light before opening a PR (R6 v3 / #17 M7c)
op-receive-feedback.md	When to Use, Prerequisites, Procedure, Examples, Error Handling

agent-messaging skill (global) — Messaging commands.

Governance

This skill operates under the AI Maestro approval tiers — the escalation ladder Tier 0 (self-authority for in-scope work + DERIVED NPT/EHT tasks) → CHIEF-OF-STAFF → MANAGER → USER. See the ampa-prrd-trdd-kanban skill and ~/.claude/rules/trdd-approval-tiers.md for which transitions need approval. A MEMBER never self-approves its own releases — entering the release pipeline (publish/deploy) is USER/MANAGER-authorized, and the INTEGRATOR (not the MEMBER) owns the → complete flip.

Related

• ampa-task-execution — Core task implementation workflow triggering communication.
• ampa-handoff-management — Task handoff protocols depending on completion notifications.