cross-agent-trigger

What problem does it solve?

Cross-agent-trigger turns inbound email triage outcomes into correctly routed specialist work so complex incidents don’t stall behind email classification.

Core Features & Use Cases

• Detects specialist-required categories: Maps classified email categories (e.g., Meraki/network, Azure/Entra, AWS, NetSuite, security incidents) to the appropriate specialist agent instead of handling everything inside email triage.
• Creates a Jira system-of-record: Generates a Jira ticket that links the email source to downstream agent execution and tracking.
• Dispatches a structured mission with full email context: Sends a self-contained mission prompt via the ClaudeClaw mission queue so the specialist can act immediately.
• Acknowledges the reporter with routing status: Confirms routing back to the email reporter with the Jira reference and priority.

Quick Start

Invoke cross-agent-trigger after classify-ticket has produced a category that maps to a specialist agent, and provide the email subject or message-id so it can fetch context, create a Jira ticket, and dispatch the specialist mission.