Orchestrate goal-driven TypeScript agent teams with Open Multi Agent
Turn a user goal into a planned multi-agent task DAG, execute independent tasks in parallel, and trace the run from a TypeScript backend.
npx skills add agentskillexchange/skills --skill orchestrate-goal-driven-typescript-agent-teams-with-open-multi-agent
Use Open Multi Agent when an operator needs a backend agent team to decompose a goal into a task DAG, assign work to specialized agents, run independent tasks in parallel, and synthesize a final result with progress and trace visibility. This is useful for repeatable engineering or analysis workflows such as code generation, contract review, meeting summarization, competitive monitoring, and other jobs where the agent should plan and coordinate multiple roles rather than answer in a single chat turn. Invoke it instead of using a normal product UI when the workflow belongs inside a Node.js/TypeScript service or CLI and needs explicit teams, provider selection, tools, optional MCP connections, structured output, shared memory, and observable execution. The scope boundary is the concrete runTeam/runTasks operator workflow for goal-to-DAG orchestration; it is not a generic multi-agent framework listing, an SDK card, or a broad MCP product entry.
What this skill actually does
Inputs and prerequisites: Node.js >= 18, npm, API keys for selected model providers or local model provider, optional MCP servers.
Setup notes: Install with `npm install @open-multi-agent/core`, define AgentConfig entries for the team, create an OpenMultiAgent orchestrator, then call `runTeam(team, goal)` or `runTasks()` from a TypeScript backend or run examples with `npx tsx examples/.ts`.
Source and verification boundary: use https://github.com/open-multi-agent/open-multi-agent as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.