yofine/mexus/run

/mexus-skill:run

Use this skill when the user invokes /mexus-skill:run.

This command executes work from the active Agent Team kanban. It does not create a Mission and it does not start the board. By default it targets the latest active Mission created by /mexus-skill:team.

Steps

1. Locate the active mission under agent-team/missions/, or use --name <mission-name> if provided. If no active lifecycle marker exists, fall back to the newest mission.
2. Read:

• agent-team/mission-workflow.md
• agent-team/agents.md
• agent-team/missions/<mission-name>/mission.md
• agent-team/missions/<mission-name>/agents.md
• agent-team/missions/<mission-name>/kanban.md
• agent-team/missions/<mission-name>/roundtable.md
• agent-team/missions/<mission-name>/squad-lead.md

1. Act as Squad Lead for task selection and dispatch. Do not execute or fill another Agent's task result.
2. Select the next actionable tasks from To Claim.
3. Use the Agent tool to start background Agents in parallel for the selected task batch. Respect --limit <count> when present; otherwise dispatch a small safe batch.
4. Require every background Agent to claim, update, and complete its own task block in kanban.md before reporting back.
5. Review completed tasks only when the task publisher is Squad Lead, or when the mission workflow says the current lead owns the acceptance standard.
6. Perform mission-level acceptance after publisher reviews. If the overall result is below expectation, publish new focused tasks to the responsible Agents.

Background Agent Prompt Requirements

Every background Agent prompt must include:

• Mission name.
• Agent name and responsibility from mission agents.md.
• Agent names must follow agent-team-mission-workflow: short stable names from the Ars Goetia / Lesser Key of Solomon name set.
• Exact current task block from kanban.md.
• A clear statement that this is the first/current assigned task, not all future work.
• Requirement to read the mission files before editing.
• Requirement to claim the task by moving the full task block to In Progress.
• Requirement to write Result, Files, Verification, and Updated in its own task block.
• Requirement to move the task to Done only after verification.
• Requirement to leave Review for the publishing Agent named in From.
• Instruction to prioritize kanban-assigned work.
• If the task is outside its responsibility and the correct owner is clear, reassign it in kanban.md with a brief reason in Updated.
• If ownership is unclear, publish a clarification task assigned to the Squad Lead.
• No Mexus server, pane dispatch, Mission Inbox, or external A2A dependency.

Rules

• Kanban is the source of truth.
• Squad Lead is a fixed coordination role name and is not an execution Agent name.
• Kanban task From must be Squad Lead or an executing Agent, never User.
• Every work item follows publisher acceptance: publisher creates task, executor completes and self-tests, publisher fills Review.
• Squad Lead owns mission-level acceptance and publishes new tasks for gaps instead of rewriting another Agent's task result.
• After meaningful completed work is accepted, update the repository-level agent-team/agents.md roster with the Agent's durable module ownership, known strengths, and Work history. Do not put mission-specific prompts in the repository roster.
• By default, execute only the current active Mission. Archived Missions are historical unless the user explicitly passes --name.
• The executing background Agent updates the kanban task it owns. The Squad Lead does not fill execution results for that Agent.
• Do not execute tasks that are already In Progress unless the user explicitly asks for recovery.
• Do not mutate board process state.
• Do not invent agent names when a suitable mission agent already exists.
• Publish follow-up tasks instead of crossing scope boundaries.
• Use roundtable.md for decisions that affect multiple Agents, shared interfaces, mission scope, product direction, sequencing, acceptance criteria, or major risk trade-offs. Roundtable is not a default kanban blocker.

Publisher Review

When no assigned To Claim task remains:

1. Check Done for tasks where From is the current Agent and Review has no accepted marker.
2. Review only those tasks.
3. If accepted, fill Review.
4. If rejected, publish a focused fix task under To Claim.

Output

After dispatching or executing work, report:

• Mission name.
• Tasks selected.
• Background Agents dispatched.
• Any tasks reassigned or clarification tasks created.
• Verification status for completed tasks.