metabot-team

# MetaBot Agent Teams CLI This Skill documents the `metabot teams` command surface and its durable-state semantics. It does not define Agent execution policy. ## Core Model Team = Agents + Messages + Tasks + Runs. - Agents retain a stable Team identity across engine Sessions. - Messages are the normal conversational handoff surface. - Tasks record durable assignment, dependencies, status, and result. - Runs record individual executions, output, failure, retry, cancellation, and card state. - Multiple dispatches to the same Agent create independent Tasks and Runs. ## Inspect A Team ```bash metabot teams status <team> --summary metabot teams agents list <team> metabot teams tasks list <team> --summary metabot teams runs list <team> --summary metabot teams next <team> <member> --summary ``` `--summary` or `--plain` selects concise output. The default output is JSON. ## Create And Dispatch ```bash metabot teams create <team> --description "..." metabot teams agents spawn <team> <member> --role <role> --prompt "..." metabot teams dispatch <team> <member> "<subject>" --description "..." --plain metabot teams send <team> <member> "<message>" --from <sender> metabot teams inbox <team> <member> --summary ``` `dispatch` creates the Task/message/Run projection used by the supervisor. A teammate's final response returns through Team state and the configured display destination. The default maximum parallel Runs per Agent is `4`, configurable with `METABOT_AGENT_TEAM_MAX_PARA...