emasoft/amia-integration-protocols

Shared References

Overview

Shared reference documents used across Integrator Agent skills. Contains common patterns, protocols, and utilities for consistent behavior.

Prerequisites

No external dependencies required.

Instructions

1. Identify the shared protocol or pattern needed for the current task
2. Review the relevant reference document from the list below
3. Apply the protocol or pattern to the agent workflow
4. Validate the implementation against the documented schema
5. Document any handoff or session state according to the standard format

Checklist

Copy this checklist and track your progress:

• [ ] Verify requesting agent's team membership via team-governance skill
• [ ] Identify the shared protocol or pattern needed
• [ ] Review the relevant reference document
• [ ] Apply the protocol or pattern to the workflow
• [ ] Validate implementation against documented schema
• [ ] Document handoff or session state in standard format
• [ ] Verify all required fields are present in handoff payload
• [ ] Ensure datetime fields use ISO 8601 format

Output

| Output Type | Format | Description | |-------------|--------|-------------| | Handoff Payload | JSON | Structured agent handoff with context and state | | Session State | JSON | Current session state snapshot for continuity | | Coordination Protocol | JSON | Multi-agent workflow coordination structure |

Error Handling

Validate handoff payloads before sending. Required fields: handoff_type, from_agent, to_agent, context. All datetime fields must use ISO 8601 format.

Resources

• handoff-protocols — Handoff protocol reference:
  • Document Delivery Protocol
  • Task Delegation Protocol
  • Acknowledgment Protocol
  • Completion Reporting Protocol
  • Blocker Escalation Protocol
  • Troubleshooting
• ai-maestro-message-templates — Message templates:
  • 1.0 Standard AI Maestro Messaging Approach
  • 2.0 Receiving Messages from Orchestrator (AMOA)
  • 3.0 Sending Messages to Sub-Agents
  • 4.0 Reporting Results to Orchestrator (AMOA)
  • 5.0 Quality Gate Communication
• sub-agent-role-boundaries-template — Role boundaries:
  • Core Identity: Worker Agent (Not Orchestrator)
  • Standard Output Format
  • Communication Rules
  • Tool Restrictions
  • Common Constraints Template
  • Success/Completion Conditions
  • Anti-Patterns to Avoid
• routing-checklist — Routing checklist:
  • Sub-Agent Routing Table
  • Routing Decision Guidelines
  • Priority Triage
  • Success Criteria Checklist
  • Routing Decision Checklist
• record-keeping — Record-keeping:
  • 1. Routing Log Format
  • 2. Integration Status Files
  • 3. Quality Reports
  • 4. Session State Structure
  • Best Practices
• phase-procedures — Phase procedures:
  • Phase 1: Request Reception
  • Phase 2: Routing Decision
  • Phase 3: Delegation
  • Phase 4: Monitor Completion
  • Phase 5: Report to AMOA

Examples

# Send a handoff payload from integrator to orchestrator
amp-send.sh amoa-main "Integration Complete" '{
  "handoff_type": "task_completion",
  "from_agent": "amia-main",
  "to_agent": "amoa-main",
  "context": {"pr": 42, "status": "merged", "branch": "feature/auth"},
  "timestamp": "2026-03-26T12:00:00Z"
}'

Expected result: The orchestrator receives a structured handoff payload with all required fields (handoff_type, from_agent, to_agent, context) and can update its task tracking accordingly.