amama-github-routing

Route GitHub issues, PRs, projects, and releases to specialists using team labels and UUID tracking.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/Emasoft/ai-maestro-assistant-manager-agent --skill amama-github-routing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: amama-github-routing
Source: https://github.com/Emasoft/ai-maestro-assistant-manager-agent/tree/main/skills/amama-github-routing
Command: npx skills add https://github.com/Emasoft/ai-maestro-assistant-manager-agent --skill amama-github-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Route GitHub operations (issues, PRs, Kanban/Projects, releases) to the appropriate AI Maestro specialist based on operation type, team labels, and context, ensuring boundary enforcement and traceable handoffs.

Core Features & Use Cases

  • Route items to AMIA, AMAA, or AMOA according to operation type and context.
  • Enforce team boundaries with mandatory team labels and escalate cross-team cases via AMAMA.
  • Provide handoff templates, UUID tracking, and bidirectional task-sync with the AI Maestro task system.
  • Support design-linked routing, module-task routing, and Kanban-to-task synchronization.

Quick Start

Route a GitHub operation to AMIA by applying a team label and issuing a standard handoff.

Frequently Asked Questions about amama-github-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route GitHub issues and pull requests to the right team specialist?▼

Route GitHub issues and PRs to specialists by evaluating operation type, team labels, and context, then applying a standard handoff template with UUID tracking to ensure traceable, auditable routing within the AI Maestro system.

What is the best way to enforce team boundaries when managing GitHub Kanban projects?▼

Enforce team boundaries in GitHub Kanban projects by applying mandatory team labels and escalating cross-team cases via AMAMA, ensuring operations route only to the correct designated specialist without overlap.

How does bidirectional task-sync work between GitHub Projects and the AI Maestro task system?▼

Bidirectional task-sync links GitHub Kanban project items with the AI Maestro task system using UUID tracking, ensuring that status changes and routing decisions remain synchronized and traceable across both platforms.

Can I route design-linked or module-context GitHub operations to a specific specialist?▼

Yes, design-linked and module-context GitHub operations route directly to AMAA or AMOA specialists based on operation context and team labels, providing specialized handoff templates and boundary enforcement for each case.

Do I need team labels to use GitHub routing for AI Maestro handoffs?▼

Yes, mandatory team labels are required to route GitHub operations to the appropriate AI Maestro specialist, as they determine boundary enforcement and ensure correct handoff targeting without ambiguity.

What happens when a GitHub issue spans multiple teams and crosses boundaries?▼

Cross-team GitHub issues escalate via AMAMA, which handles boundary violations by providing decision trees and handoff templates to resolve routing conflicts while maintaining UUID tracking for full auditability.