pi-messenger

Coordinate multi-agent task execution with join, plan, work, and status operations.

Updated May 4, 2026
One-click install
npx skills add https://github.com/panamini/pi-tooling --skill pi-messenger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-messenger
Source: https://github.com/panamini/pi-tooling/tree/main/skills/pi-messenger
Command: npx skills add https://github.com/panamini/pi-tooling --skill pi-messenger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you organize multiple agents so they can claim work, plan together, and communicate progress without chaotic overlaps.

Core Features & Use Cases

  • Crew/task orchestration: Manage parallel execution by running the messenger UI.
  • Structured automation: Use pi_messenger() to join, plan, assign work, and track task status.
  • Workflow coordination: Coordinate larger implementation batches where multiple agents need shared context and reservations.

Quick Start

Run /messenger to open the crew/task management UI for coordinating your agents in the current project.

Frequently Asked Questions about pi-messenger

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

FAQPage Schema
How do I coordinate multiple agents to prevent overlapping work in parallel execution?

Multi-agent coordination prevents overlapping work by managing crew membership, shared planning, and task status tracking. Agents claim work and reserve resources through structured messaging, ensuring parallel execution happens without chaotic conflicts.

What is the best way to track agent work claims and task status across a project?

Tracking agent work claims uses an internal orchestration loop exposing task.* and status operations. This manages crew membership and task reservations, providing shared context so multiple agents can monitor progress and coordinate implementations deterministically.

How do I set up workflow orchestration for parallelized agent workstreams?

Workflow orchestration for parallelized workstreams requires running the messenger entry point to open the crew management UI. From there, you join the crew, plan tasks, assign work, and track execution using deterministic command handling.

Can I use this for coordinating larger implementation batches with multiple agents?

Yes, this fits scenarios involving coordinated implementation batches with multiple agents. It provides the shared context, planning, and task reservations needed to manage parallel execution where agents must claim work and communicate progress.

Do I need any external dependencies to run the multi-agent task planning and messaging loop?

No external dependencies are required. The internal orchestration loop handles agent coordination by exposing join, plan, work, task.*, and status operations through deterministic command handling within your current project environment.