القائمة
Use when the user invokes `$wave`, asks to start or enter a multi-agent wave, or asks to spin up / set up a wave for a batch of tasks coordinated across agents.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the current repo is explicitly governed by team-collab: `obsidian-docs/` exists in cwd/ancestor, repo `AGENTS.md`/`CLAUDE.md` imports team-collab, the cwd is under a registered code/docs path, or the user asks for team-collab handoff/checkpoint/docs governance/Feishu automation. Do not use solely because a global config file exists.
Use when the user invokes `$digest`, asks for a multi-agent wave digest or progress summary, or asks "what's the status of the wave" / "where are things".
Use when the user invokes `$gate`, asks whether a PR/merge is ready, asks to gate-check or merge-gate a multi-agent task, or asks "can this merge?".
Use when the user invokes `$checkpoint`, asks for a checkpoint, or asks to update CURRENT/NEXT/RISKS/TODO without committing or pushing.
Use when the user invokes `$docs-refresh`, asks to update Obsidian project docs from a stale audit/dev record, or wants old docs archived while active docs become current.
Use when the user invokes `$handoff`, asks for a handoff, or asks to finish a team-collab session by updating CURRENT/NEXT/RISKS/TODO and syncing docs.
| name | wave |
| requires_protocol | >=0.6.0,<0.7.0 |
| description | Use when the user invokes `$wave`, asks to start or enter a multi-agent wave, or asks to spin up / set up a wave for a batch of tasks coordinated across agents. |
This is a Codex-friendly command wrapper for the multi-agent wave entry point. Codex does not currently support arbitrary custom top-level slash commands like /wave, so the supported Codex entry point is:
$wave <slug-or-goal>
A wave is a batch of multi-agent work coordinated entirely through committed files. $wave is the human→coordinator shortcut for starting or entering one, so you don't have to type the full multi-agent enable / multi-agent init CLI flags by hand.
team-collab-protocol skill and its references/multi-agent.md flow. If the protocol skill is not available in the current session, read ~/.codex/skills/team-collab-protocol/SKILL.md; if that file is missing, stop and tell the user to run team-collab install-skills --agent codex --force.command -v team-collab. If missing, stop and tell the user to install the CLI with npm install -g @embodot/collab@latest, then refresh skills with team-collab install-skills --agent codex --force if needed.$wave as a slug only when it is a single token matching ^[a-z][a-z0-9-]{2,63}$. Otherwise, treat it as a goal, derive a slug, and confirm the slug with the user before creating anything.team-collab multi-agent enable
team-collab multi-agent init --slug <slug>
<slug-or-goal> was a free-text goal rather than a slug, read the generated multi-agent/<slug>/PRD.md and pr-plan.md and draft a first cut of the wave plan (goal, task breakdown, suggested roles) into them, then tell the user what you drafted and ask for confirmation.multi-agent/<slug>/PRD.md, pr-plan.md, and any existing agent-runs/**, then summarize the current wave state to the user.references/multi-agent.md for the wave layout, ownership, and command boundaries. Do not improvise task assignments from this wrapper alone — present the plan and let the user, coordinator, or CLI task lifecycle commands drive the next step.If a future Codex version supports custom slash commands and /wave reaches the model as plain user text, handle it exactly the same way as $wave.