acp-triggered-coordination

Trigger agent reviews of GitHub artifacts via ACP and route responses through GitHub surfaces.

Updated Apr 1, 2026

Search Tags:#workflow #github #agents #coordination #issues #pull-requests #acp

Ready to run

npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill acp-triggered-coordination

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acp-triggered-coordination
Source: https://github.com/lilmuckers/agentic-team-plugin/tree/main/skills/acp-triggered-coordination
Command: npx skills add https://github.com/lilmuckers/agentic-team-plugin --skill acp-triggered-coordination

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use ACP to trigger attention, not to replace durable external context. Use when one agent needs another agent to review a visible artifact and respond through the appropriate GitHub surface rather than through hidden chat alone.

Core Features & Use Cases

Trigger agent review requests on external artifacts (GitHub issues, PRs, wiki pages).
Route responses through the correct GitHub surface rather than private agent chat.
Supports coordination among Builder, Spec, QA, and specialists.

Quick Start

Instruct ACP to notify the relevant agent to inspect the target artifact on GitHub.

Frequently Asked Questions about acp-triggered-coordination

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

FAQPage Schema

How do I coordinate multiple GitHub agents to review issues and pull requests?▼

Agent coordination on GitHub issues and pull requests uses ACP to trigger review requests on visible artifacts, routing responses through the correct GitHub surface instead of hidden chat. You notify the relevant specialist agent to inspect the target artifact directly on GitHub.

What is the best way to trigger a QA agent review on a GitHub pull request?▼

Triggering a QA agent review on a GitHub pull request uses ACP to send clear instructions referencing the artifact, prompting the specialist to respond through the appropriate GitHub surface. This ensures review feedback remains visible and durable.

Can I route agent responses through GitHub surfaces instead of private chat?▼

Routing agent responses through GitHub surfaces is supported by using ACP to trigger attention on external artifacts like issues and wiki pages. Agents respond directly on the GitHub surface rather than through hidden private chat.

Does ACP coordination work for Builder, Spec, and QA specialist agents?▼

ACP coordination works for Builder, Spec, QA, and other specialist agents by triggering review requests on visible GitHub artifacts. The coordination requires clear trigger instructions and artifact references for the respective agents to inspect and respond.

When should I not use ACP for agent coordination on GitHub artifacts?▼

ACP for agent coordination should not be used to replace durable external context. It is designed specifically to trigger agent attention for reviewing visible artifacts and routing responses through GitHub surfaces, not for managing internal hidden chat context.