菜单
Create MAPS M2 Roster for a multi-agent system. Use after M1 System Shape selects Multi-Agent / MAPS to define participants, human owners, roles, candidate agents, tools/services, responsibilities, authority category, memory scope, and the evidence needed before contracts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | multi-agent-roster |
| description | Create MAPS M2 Roster for a multi-agent system. Use after M1 System Shape selects Multi-Agent / MAPS to define participants, human owners, roles, candidate agents, tools/services, responsibilities, authority category, memory scope, and the evidence needed before contracts. |
Current version: 0.1.0.
Follow semantic versioning for this skill:
When changing this skill, update Current version and add a Changelog entry with the date, version, and short summary of behavior changed.
Use /multi-agent-roster at M2 after M1 chooses Multi-Agent / MAPS. M2 decides who or what belongs in the system before contracts, coordination, capabilities, or orchestration are designed.
At the start of every project run, look for project-foundation.md. If it exists, read Persistent Memory Contract and use its configured notes, sources, memory, RAG, and sync rules as the project defaults. If .maps/foundation-preferences.json exists, use it as the structured preference source for automation.
When this skill creates durable knowledge, write it through the shared MAPS memory helper. The helper gives this skill its own named note under the configured notes root, mirrors that note into the configured RAG location when one exists, appends MAPS Skill Run Log, and records a RAG reindex manifest.
At the end of the run, call the helper after creating the primary output artifact:
python "$CODEX_HOME/skills/foundation/scripts/maps_memory.py" complete-run --project . --skill /multi-agent-roster --phase M2 --output "<primary artifact path>" --summary-file "<primary artifact path>" --memory-updates "<notes, sources, memory, or RAG updates>"
If the helper is unavailable, manually append the timestamp, skill, phase, output path, memory updates, and short note to project-foundation.md, then update this skill's named note in <notesRoot>/maps-runs/.
Read assets/maps/catalogs/multi-agent-research-sources.md when available. Use role-pressure, A2A discovery/capability ideas, OpenAI handoff guidance, and NIST governance controls to decide which participants deserve first-class status.
Ask exactly one question at a time. Do not present the user with a multi-question form, checklist, or table to fill out.
Start with:
What outcome requires more than one participant instead of one agent?
Then ask only the next missing question needed to identify participants, owners, responsibilities, authority, memory, tools, risk, and proof.
project-foundation.md, M1 system-shape.md, and any roles or agent briefs already present./role.m/<project-handle>/roster.md from templates/multi-agent-roster.md.When the skill is complete, tell the user explicitly. Do not end with only files changed or raw output.
Report:
/multi-agent-contracts when retained participants are clear, or /role when required role contracts are missing.If the skill is blocked, say what answer, artifact, access, approval, or tool is needed before the next skill can run.
m/<project-handle>/roster.mdMAPS Phase 3 Build skill that merges base /build-agent, incremental implementation, and test-driven development into one implementation workflow.
Run MAPS Phase 6 Deploy by wrapping /deploy-agent with GitHub Actions environments and Cloudflare deployment automation. Use when Codex needs GitHub to deploy a Cloudflare Pages, Workers, or Agents project; replace manual Wrangler deploys; configure workflow gates, encrypted secrets, smoke tests, release evidence, and rollback records.
Create the MAPS Design phase artifact for an agent or multi-agent system. Use when defining roles, workflows, handoffs, memory, context, guardrails, approvals, escalation paths, test-first proof requirements, and system boundaries from an agent brief.
Run enhanced MAPS M8 Experience Design for websites, SaaS products, dashboards, landing pages, and agent-facing product surfaces. Use when Codex needs to wrap /design-experience with website design references, component-system choices, accessibility primitives, UX/service-design reasoning, responsive layout, page hierarchy, and production-ready UI handoffs.
Run MAPS M8 Experience Design for multi-agent products, or optional A2 Experience Design for single-agent products without an M layer. Use when Codex needs to turn product intent, orchestration behavior, agent behavior, and product constraints into user journeys, surfaces, information architecture, interaction states, accessibility requirements, and system-evaluation handoffs.
Run MAPS Phase 5 Evaluate by wrapping the base Evaluate process with LangSmith, Inspect AI, and Phoenix. Use when Codex needs to create eval suites, trace-backed eval runs, safety/tool-use checks, regression evidence, eval reports, or Phase 7 observability handoff for an equipped agent.