菜单
Use pi-messenger for multi-agent coordination and Crew task orchestration. Covers joining the mesh, planning from PRDs, working on tasks, file reservations, and agent messaging. Load this skill when using pi_messenger or building with Crew.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create or update Pi skills (SKILL.md plus optional scripts, references, or assets). Use when someone asks to design a new Pi skill, refine an existing one, or structure skills for Pi discovery or packaging.
Guide for extending Pi — decide between skills, extensions, prompt templates, themes, context files, or custom models, then create and package them. Use when someone wants to extend Pi, add capabilities, create a skill, build an extension, or make a Pi package.
Long-running iterative development loops with pacing control and verifiable progress. Use when tasks require multiple iterations, many discrete steps, or periodic reflection with clear checkpoints; avoid for simple one-shot tasks or quick fixes.
Cheat sheet + workflow for launching interactive coding-agent CLIs (Claude Code, Gemini CLI, Codex CLI, Cursor CLI, and pi itself) via the interactive_shell overlay or headless dispatch. Use for TUI agents and long-running processes that need supervision, fire-and-forget delegation, or headless background execution. Regular bash commands should use the bash tool instead.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Web search and content extraction via Brave Search API. Use for searching documentation, facts, or any web content. Lightweight, no browser required.
| name | pi-messenger-crew |
| description | Use pi-messenger for multi-agent coordination and Crew task orchestration. Covers joining the mesh, planning from PRDs, working on tasks, file reservations, and agent messaging. Load this skill when using pi_messenger or building with Crew. |
Use pi-messenger for multi-agent coordination and Crew task orchestration.
pi_messenger({ action: "join" })
pi_messenger({ action: "status" })
pi_messenger({ action: "list" }) // See other agents
pi_messenger({ action: "crew.install" })
pi_messenger({ action: "crew.agents" }) // Verify 5 agents
// Auto-discover PRD.md in current directory
pi_messenger({ action: "plan" })
// Or specify path
pi_messenger({ action: "plan", prd: "path/to/PRD.md" })
// Single wave (runs ready tasks once)
pi_messenger({ action: "work" })
// Autonomous (keeps running until done/blocked)
pi_messenger({ action: "work", autonomous: true })
pi_messenger({ action: "task.list" })
pi_messenger({ action: "task.ready" }) // Tasks with no pending deps
pi_messenger({ action: "task.show", id: "task-1" })
pi_messenger({ action: "task.start", id: "task-1" })
pi_messenger({ action: "task.done", id: "task-1", summary: "What was done" })
pi_messenger({ action: "task.block", id: "task-1", reason: "Why blocked" })
pi_messenger({ action: "task.unblock", id: "task-1" })
pi_messenger({ action: "task.reset", id: "task-1" })
pi_messenger({ action: "task.reset", id: "task-1", cascade: true }) // Reset dependents too
// Review a task implementation
pi_messenger({ action: "review", target: "task-1" })
// Review the overall plan
pi_messenger({ action: "review", target: "plan", type: "plan" })
// Reserve files before editing
pi_messenger({ action: "reserve", paths: ["src/index.ts", "src/types.ts"], reason: "Working on core" })
// Release when done
pi_messenger({ action: "release" })
// Rename yourself
pi_messenger({ action: "rename", name: "MyAgentName" })
// Send message to specific agent
pi_messenger({ action: "send", to: "OtherAgent", message: "Hello!" })
// Broadcast to all
pi_messenger({ action: "send", broadcast: true, message: "Announcement" })
// 1. Join
pi_messenger({ action: "join" })
// 2. Plan (spawns planner agent)
pi_messenger({ action: "plan" })
// 3. Check tasks
pi_messenger({ action: "task.list" })
// 4. Work
pi_messenger({ action: "work", autonomous: true })
// 5. Status
pi_messenger({ action: "status" })
Crew stores data in .pi/messenger/crew/:
.pi/messenger/crew/
├── config.json # Project config (concurrency, etc.)
├── plan.json # Plan metadata
├── plan.md # Planner output
├── tasks/
│ ├── task-1.json # Task metadata
│ ├── task-1.md # Task spec
│ └── ...
├── blocks/
│ └── task-N.md # Block context
└── artifacts/ # Debug artifacts
Create .pi/messenger/crew/config.json:
{
"concurrency": {
"workers": 3 // Max parallel workers (default: 2)
},
"planning": {
"maxPasses": 3 // Max planner passes before accepting last output
}
}