Help us improve
Share bugs, ideas, or general feedback.
From mexus-team
Starts a new Markdown-only Agent Team Mission for Claude Code or Codex background Agents without a Mexus server. Creates mission files, assigns agents, and starts a board.
npx claudepluginhub yofine/mexus-agent-team --plugin mexus-team-roundtableHow this skill is triggered — by the user, by Claude, or both
Slash command
/mexus-team:mission "<request>" [--name <mission-name>]"<request>" [--name <mission-name>]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user invokes `/mexus-team:mission "<request>"`.
Resumes an existing active Markdown-backed Agent Team Mission in a later Claude Code or Codex session. Use when continuing a mission started in a previous session.
Sets up multi-agent teams for complex projects with file-based planning, per-agent directories, and teammate spawning. Triggers on team/swarm/start-project requests.
Creates a multi-agent team composition file with purpose definition, member selection, coordination patterns, and registry integration. Use when formalizing recurring collaborative workflows.
Share bugs, ideas, or general feedback.
/mexus-team:missionUse this skill when the user invokes /mexus-team:mission "<request>".
This skill only creates a new Mission. To continue an already-active Mission, use /mexus-team:continue instead. A <request> argument is required.
This is a standalone Agent Team workflow. It must not call mexus, create panes, use Mission Inbox, or rely on external A2A messaging. Communication happens through agent-team/ Markdown files, especially kanban.md.
Starting a Mission makes it the only active Mission in the workspace. Any previous active Mission is archived by changing its mission.md lifecycle to Lifecycle: archived.
Preserve the user's request.
Choose a Mission name from --name or derive a short slug.
Run the standalone script from this plugin:
node <plugin-root>/scripts/start-mission.mjs --root "$PWD" --name <mission-name> --request "<request>"
Read:
agent-team/mission-workflow.mdagent-team/missions/<mission-name>/mission.mdagent-team/missions/<mission-name>/agents.mdagent-team/missions/<mission-name>/kanban.mdagent-team/missions/<mission-name>/roundtable.mdAct as Squad Lead.
Refine the generated agents.md and kanban.md so the Mission has the right execution Agents and actionable worker tasks.
After the roster and kanban are planned, start (or reuse) the read-only board so the user can watch execution:
node <plugin-root>/scripts/start-board.mjs --root "$PWD" --host 0.0.0.0
The script reuses a board that is already running for this project and only prints its URL; it starts a fresh board only when none is alive. It probes the board and API ports for up to 5 seconds before declaring success.
Verify the board actually started before continuing. Check the command's exit status and look for Agent Team board: <URL> in the output. If the exit code is non-zero, or the success line is missing, tell the user the board did not start and surface the script's diagnostic output verbatim. Common causes:
agent-team/ is missing in the current project (start the Mission first).pnpm is not on PATH. Install pnpm (https://pnpm.io/installation) and retry.4179 or 5179 (or whichever the script picked) are already in use./mexus-team:board once pnpm finishes.Do not pretend the board is up if the script reported failure. Either wait for it to recover and re-run, or proceed without a board and note that to the user. Print the board URL only when the script confirmed the board is reachable.
kanban.md, Squad Lead dispatches the next background Agents itself. The user does not run a command for in-session follow-up; /mexus-team:continue is only for resuming a Mission in a later session.Squad Lead is a fixed coordination role name. Do not rename it, and do not consume one of the execution Agent names for Squad Lead./mexus-team:mission must finish with a planned roster, planned kanban tasks, a running board, and the first background Agents dispatched.agent-team/agents.md as the long-term repository roster. Reuse existing Agents when their module history fits, and add new Agents only when no close owner exists.agent-team-mission-workflow: short stable names drawn at random from the Ars Goetia / Lesser Key of Solomon name set, never sequential placeholders. A name must not repeat another Agent in this Mission or in agent-team/agents.md.From must be Squad Lead or an executing Agent, never User.kanban.md with status, Result, Files, Verification, and Updated before reporting back.From reviews the completed task and fills Review.kanban.md with the reason in Updated.roundtable.md for decisions that affect multiple Agents, shared interfaces, mission scope, product direction, sequencing, acceptance criteria, or major risk trade-offs.Every background Agent prompt must include:
kanban.md.Done.Review for the task publisher.Acceptance names an artifact path, the Agent must write that file under agent-team/missions/<mission-name>/artifacts/ with the frontmatter described in agent-team/mission-workflow.md (## Artifacts), include the required sections, and list the artifact path in its own task's Files: field.Output language: from mission.md (default en), with the instruction to write all user-visible content in that language and keep structural words in English per agent-team/mission-workflow.md (## Output Language).start-mission.mjs writes an Output language: field into mission.md based on the original request (CJK characters → zh, otherwise en). Read that field before refining the Mission, and apply the rule from agent-team/mission-workflow.md under ## Output Language:
Request/Reason/Acceptance/Result/Verification/Review values, RoundTable field values, Squad Lead log, artifact body and artifact title) is written in that language.Lifecycle values, RoundTable section headings, artifact frontmatter keys) stay in English.When dispatching background Agents, include this rule in their prompt so the kanban they write back stays consistent.
Squad Lead is responsible for routing long-form output to artifacts rather than letting it pile up inside kanban task blocks. Apply the rules in agent-team/mission-workflow.md under ## Artifacts:
Acceptance field so it names the exact artifact path (artifacts/<YYYY-MM-DD>-<slug>.md), lists minimum sections or questions the artifact must answer, and requires the executor's Files: field to list that path.## Approved in roundtable.md, publish a follow-up kanban task that produces artifacts/<YYYY-MM-DD>-rt-<topic-slug>.md. This is not optional.rt-* artifact; every research / document task lists an artifact path in its Files: field and that file exists. Any gap is closed by publishing a new focused task, not by writing the artifact yourself on another Agent's behalf.After creating the Mission, tell the user: