emasoft-orchestrator-agent

GitHub Projects V2 kanban board management. Use when creating boards, adding columns, moving items. Trigger with kanban or column requests.

Agent progress monitoring via state-based detection. Use when tracking task completion, detecting stalls, or escalating unresponsive agents. Trigger with progress checks.

Use when coordinating work among multiple developers. Trigger with orchestration requests.

Use when replacing agents. Trigger with agent replacement or handoff requests.

Use when compiling verification checklists from requirements including module completion, quality gates, and test coverage checklists. Trigger with checklist compilation requests.

Trigger with developer communication needs. Use when communicating with human developers in code reviews, issues, technical discussions, and status updates. Covers effective communication patterns.

Trigger with Claude Code action requests. Use when setting up Claude Code in GitHub Actions for automated PR reviews, @claude mention responses, and issue triage.

Interview protocols for task verification. Use when checking implementer readiness or approving PR creation. Trigger with task assignment.

GitHub label taxonomy for multi-agent systems. Use when managing labels for issue tracking and coordination. Trigger with label requests.

AI Maestro message templates for emasoft plugins. Use when sending task assignments, status reports, or escalations between agents. Trigger with messaging requests.

Trigger with module management tasks. Use when managing modules during Orchestration Phase (add, modify, remove, prioritize, reassign). Every module maps 1:1 to GitHub Issue.

Use when managing orchestration phase commands. Trigger with start, monitor, loop control, cancellation, or stop hook enforcement requests.

Use when coordinating remote AI agents. Trigger with task delegation or multi-agent coordination requests.

Task distribution based on skills and availability. Use when assigning work to agents, balancing load, or resolving dependencies. Trigger with assignment requests.

Use when orchestrating complex projects. Trigger with multi-module or two-phase planning requests.

Use when verifying implementations. Trigger with verification, testing, or evidence requests.