菜单
Guide the user through first-run bootstrap of the MnM Governed Workflows plugin — calls setup_workspace, writes agent files, prompts /reload-plugins, and runs a verification push_local_state. Use when the user installs the plugin, runs /mnm--onboard explicitly, or asks how to "get started with MnM".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Tour guidé de la codebase MnM pour onboarder rapidement sur le projet. À invoquer quand un agent débarque sur le repo et a besoin de comprendre l'architecture en moins de 30 minutes : structure monorepo, services backend clés, conventions, feature phare (Governed Workflows). Lit proactivement les bons fichiers et résume la mental map. Utiliser via `/mnm-codebase-tour` ou laisser Claude l'auto-invoquer quand l'utilisateur pose une question d'orientation générale ("comment ça marche", "où est X", "explique-moi le projet").
Interact with the MnM control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, or call any MnM API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for MnM coordination.
Create new agents in MnM with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.
File-based memory system using Tiago Forte's PARA method. Use this skill whenever you need to store, retrieve, update, or organize knowledge across sessions. Covers three memory layers: (1) Knowledge graph in PARA folders with atomic YAML facts, (2) Daily notes as raw timeline, (3) Tacit knowledge about user patterns. Also handles planning files, memory decay, weekly synthesis, and recall via qmd. Trigger on any memory operation: saving facts, writing daily notes, creating entities, running weekly synthesis, recalling past context, or managing plans.
| name | mnm--onboard |
| description | Guide the user through first-run bootstrap of the MnM Governed Workflows plugin — calls setup_workspace, writes agent files, prompts /reload-plugins, and runs a verification push_local_state. Use when the user installs the plugin, runs /mnm--onboard explicitly, or asks how to "get started with MnM". |
You are guiding a user through first-run setup of the MnM Governed Workflows plugin. Execute these steps in order — do not skip or reorder.
Before any MCP call, verify the user is authenticated. Attempt:
mcp__mnm__authenticate
If it returns already_authenticated, continue. If it returns an auth URL, wait for the user to complete the OAuth flow, then call mcp__mnm__complete_authentication with the returned code.
If the user has multiple company memberships, the OAuth flow will return invalid_request with available_companies[]. Ask the user which company_id to use and re-attempt authentication with that value.
mnm.setup_workspace
The response shape:
{
"agents": [
{ "name": "mnm--<id>", "content": "...", "sha": "...", "target_path": "~/.claude/agents/mnm--<id>.md" }
],
"session_tools": [...]
}
For each entry in agents[], use the Write tool with file_path = target_path and content = content. Expand ~ to the user's home directory resolved from the Claude Code harness environment (on Windows: $HOME maps to C:\Users\<username>).
Do not batch the writes in a single tool call — call Write once per agent. Report progress as you go.
After all writes succeed, emit exactly this message to the user:
Action required — I've written N agent files to
~/.claude/agents/. Claude Code does not hot-reload these mid-session. Please run/reload-pluginsnow and then send me any short message (even "ok") so I can continue.
STOP. Do not proceed to Step 5 until the user confirms.
After the user confirms, call:
mnm.push_local_state with { plugin_version: "<version from plugin.json>" }
The response is { target_relative_path: "last-session.json", content: { lastPluginVersion: "<version>" } }.
Write content to ${CLAUDE_PLUGIN_DATA}/last-session.json so the SessionStart hook can detect plugin upgrades on the next session and prompt re-sync.
Tell the user onboarding is complete and list two options:
mnm.list_governed_workflows, pick the hello-world entry, then mnm.launch_governed_workflow, then walk through each step with mnm.launch_governed_step.docs/superpowers/specs/2026-04-20-governed-workflows-mvp-design.md.AGENTS_STALE from launch_governed_step after onboarding means the user skipped Step 4. Ask them to run /reload-plugins and retry.MISSING_TOOLS means the plugin is misconfigured — surface error.data.required[] verbatim and stop.error.code and error.hints[] verbatim; do not attempt to recover silently.