# agent-communication

Adopt this skill: https://proskills.md/skills/other/codeaholicguy-ai-devkit-skills-agent-communication

Page: https://proskills.md/skills/other/codeaholicguy-ai-devkit-skills-agent-communication
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: skills/agent-communication/SKILL.md
size: 1285
sha: 23cc7374ec3fb3fad229b0bc6860f1c84ff5c27a
upstream: https://github.com/codeaholicguy/ai-devkit/blob/main/skills/agent-communication/SKILL.md

````text
---
name: agent-communication
description: AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send. Use when an agent needs to find another active agent, read its recent context, send it information, or request information back.
---

# Agent Communication

Use `ai-devkit agent ...` to discover and communicate with active agents. If `ai-devkit` is not on PATH, use `npx ai-devkit@latest agent ...`.

## Commands

```bash
ai-devkit agent list --json
ai-devkit agent detail --id <agent-name> --json --tail 20
ai-devkit agent send --id <agent-name> "<message>"
ai-devkit agent send --id <agent-name> --wait --timeout 120000 --json "<message>"
<command> 2>&1 | ai-devkit agent send --id <agent-name> --stdin
```

## Notes

- `list --json` returns active agents with fields such as `name`, `type`, `status`, `summary`, `projectPath`, and `lastActive`.
- Use the `name` from `list --json` as `--id`. Partial matches are supported, but exact names are safer.
- Use `detail --json --tail <n>` to read recent context from an agent before deciding what to send.
- `send --wait` waits for a reply; add `--json` when the response should be machine-readable.
- `send --stdin` forwards piped command output or larger text.
````

## File: skills/agent-communication/agents/openai.yaml
size: 227
sha: 4fff609095513d40d0de72cd9fc0b0bbc484b1b5
upstream: https://github.com/codeaholicguy/ai-devkit/blob/main/skills/agent-communication/agents/openai.yaml

```text
interface:
  display_name: "Agent Communication"
  short_description: "AI DevKit · Message active AI agents"
  default_prompt: "Use $agent-communication to exchange information with another active AI agent through AI DevKit."
```

## File: README.md
upstream: https://github.com/codeaholicguy/ai-devkit/blob/main/README.md

````text
# AI DevKit

> English | [中文](./README-zh.md)

**The control plane for AI coding agents.**

![](agent-console-showcase.jpg)

AI DevKit gives Claude Code, Codex CLI, Gemini CLI, opencode, Pi, Cursor, GitHub Copilot, Devin, and other coding agents one local-first operating layer: one config, one console, local memory retrieval, cross-agent communication, and composable engineering skills led by `dev-lifecycle`.

- **One config for every agent** — `.ai-devkit.json` reconciles setup across the coding tools your team uses
- **One console for running sessions** — `agent console` is a live TUI dashboard for supervising local agents across providers
- **Cross-agent communication** — `agent send` lets you route prompts, logs, and test output to running agents
- **Memory retrieval without context bloat** — `@ai-devkit/memory` stores decisions, conventions, and fixes in local SQLite so agents search when needed instead of carrying everything in every prompt
- **Composable engineering skills** — `dev-lifecycle`, `verify`, `tdd`, review, debugging, security, docs, and simplification skills combine into reliable workflows

The future is many AI coding agents. AI DevKit is the layer that makes them manageable.

Run machine setup once, then `init` in each project:

```bash
npx ai-devkit@latest setup
cd your-project
npx ai-devkit@latest init
```

`setup` installs built-in skills globally, session hooks, and the memory MCP wiring for detected agents.

The `kiro`, `copilot`, `devin`, and `muse` targets detect `~/.kiro`, `~/.copilot`, `~/.config/devin`, and `~/.config/muse`, respectively. Copilot skills use the `github` environment and `~/.copilot/skills`; Devin and Muse use `~/.config/devin/skills` and `~/.config/muse/skills`. Kiro has no skill environment or root defined, so its target only detects the marker and reports the memory MCP skip. All four skip memory MCP wiring until a global config writer is verified.

`init` writes project-local config. Your project gets:

| What you need | What AI DevKit installs |
|---------------|-------------------------|
| One setup source | `.ai-devkit.json` for the agents and workflow you choose |
| Running-agent visibility | `agent list`, `agent detail`, and `agent console` |
| Addressable agents | `agent send`, `--stdin`, `--wait`, and agent groups where supported |
| Retrieval-based memory | Local SQLite memory exposed through MCP and CLI, searched only when useful |
| Composable senior-engineer workflow | `dev-lifecycle` plus verification, TDD, debugging, review, security, docs, and simplification skills |

[![npm version](https://img.shields.io/npm/v/ai-devkit.svg)](https://www.npmjs.com/package/ai-devkit)
[![npm downloads](https://img.shields.io/npm/dt/ai-devkit.svg)](https://www.npmjs.com/package/ai-devkit)
[![GitHub stars](https://img.shields.io/github/stars/Codeaholicguy/ai-devkit.svg?style=social)](https://github.com/Codeaholicguy/ai-devkit)
[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)

## Who this is for

Developers whose AI coding setup has grown from one assistant into a small, messy team of agents:

- multiple terminals with no shared control surface
- separate `CLAUDE.md` / `.cursor/rules` / `AGENTS.md` / MCP setup per tool
- no easy way to send context, logs, or follow-up work to a running agent
- the agent forgetting yesterday's conventions
- "I've successfully implemented the feature" with a red build
- the agent diving into code without a plan and producing the wrong thing

Before AI DevKit, your agents are powerful but scattered. After AI DevKit, they have shared setup, a control surface, searchable memory, communication paths, and reusable skills that travel with your repo without bloating every prompt.

| Without AI DevKit | With AI DevKit |
|-------------------|----------------|
| You manage agents as isolated terminal tabs | You supervise them from `ai-devkit agent console` |
| You hand-maintain every agent setup | One config reconciles agent files, skills, and MCP setup |
| You copy logs and context between sessions | `agent send` routes prompts and stdin to running agents |
| You repeat project rules in every chat | Agents retrieve relevant memory and docs only when useful |
| The agent jumps from prompt to code | `dev-lifecycle` guides requirements, design, planning, implementation, testing, and review |
| "Done" means the agent stopped editing | "Done" requires fresh verification output |

## Start in 30 seconds

```bash
npx ai-devkit@latest setup
cd your-project
npx ai-devkit@latest init
```

Run `setup` once per machine, then `init` per project. Pick your agents, install the control-plane pieces you need, and give every tool the same operating model. Re-run `init` whenever your agent list or workflow changes.

Multi-agent orchestration (lead plus workers): **[docs guide](https://ai-devkit.com/docs/17-multi-agent-orchestration/)**.

Here's what lands in your repo:

```
your-project/
├── .ai-devkit.json              # single source of truth (re-run init anytime)
├── .claude/                     # or .cursor/, .codex/, etc. per agent you picked
│   ├── skills/                  # dev-lifecycle, verify, memory, tdd, ...
│   └── …                        # Claude: project MCP in `.mcp.json`; memory MCP wired globally by `setup`
└── docs/ai/
    ├── requirements/            # phase 1 — what to build, why
    ├── design/                  # phase 2 — how it'll be built
    ├── planning/                # phase 3 — task-by-task plan
    ├── implementation/          # phase 4 — execution notes
    └── testing/                 # phase 5 — coverage strategy
```

## Operate agents like infrastructure

AI DevKit ships an agent control plane for everyday multi-agent work:

```bash
# List running sessions across providers
ai-devkit agent list

# Open the live terminal UI
ai-devkit agent console

# Send a prompt to a running session and wait for the response
ai-devkit agent send "run the tests and report back" --id <agent-name> --wait

# Pipe multi-line output into a running session
npm test 2>&1 | ai-devkit agent send --id <agent-name> --stdin

# Send a prompt to a saved group of agents
ai-devkit agent send "review this branch for release risk" --group reviewers

# Pipe a session through Telegram — operate your agent from your phone
ai-devkit channel start telegram --agent <agent-name> --daemon
```

Use this when work spans long-running agents, multiple providers, scheduled checks, review loops, or remote control from another channel.

## Add memory without bloating context

AI DevKit memory is local SQLite knowledge for project decisions, coding conventions, and reusable fixes. Agents retrieve it when a task needs context instead of carrying every fact in every prompt.

```bash
# Store a reusable project convention
ai-devkit memory store \
  --title "API handlers return DTOs" \
  --content "REST handlers should return response DTOs instead of domain entities." \
  --tags "api,backend" \
  --scope "repo:codeaholicguy/ai-devkit"

# Search before related work
ai-devkit memory search --query "API response convention"
```

## Compose engineering workflows with skills

The control plane is useful on its own. For larger or riskier changes, AI DevKit also installs composable skills that make agents behave more like an engineering team.

`dev-lifecycle` is the anchor skill. It guides the agent through requirements, design, planning, implementation, testing, and review. Other skills plug into that flow:

- `memory` retrieves relevant project knowledge without stuffing all context into the session
- `verify` blocks completion claims without fresh test or build evidence
- `tdd` pushes test-first implementation when behavior changes
- `dev-debug` keeps debugging reproducible instead of guess-and-patch
- `security-review`, `document-code`, and `dev-simplify` add focused review passes when the task needs them

### Get the full engineering workflow sta
````
