菜单
Shared intake protocol for mastermind — rich-prompt detection, comprehensive intake questions asked one at a time, and LLM-decide logic. Never invoked directly; called by master and standalone domain commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Tech Port — deep-analyzes a foreign project, reviews the current monomind target to avoid conflicts and duplication, produces a scored port plan with mono-branded naming, and executes approved ports with full brand normalization.
Mastermind skills — list, sync, and map skills available to org agents. Scans .claude/skills/ directory and shows which roles have access to which skill domains.
Mastermind access — manage org membership roles (owner/admin/operator/viewer), granular permission grants, invite tokens, and pending join requests. Controls who can do what inside an org.
Mastermind activity — full activity feed for an org with event-type filtering, actor lookups, and entity name resolution. Fetches up to 200 recent events across issue, project, goal, agent, and routine entity types. Mirrors Activity.tsx.
Mastermind adapter-manager — global instance-level adapter catalog. Lists all built-in and npm-installed adapters, enables/disables them in menus, reinstalls from npm to pick up updates, adds custom HTTP adapters, and removes custom ones. Complements mastermind:adapters (per-org) with the global registry. Mirrors AdapterManager.tsx.
Mastermind adapters — install, enable, disable, reload, and remove LLM adapter plugins per org. Supports claude-local, gemini-local, codex-local, cursor, hermes, http, and custom adapters.
| name | mastermind-intake |
| description | Shared intake protocol for mastermind — rich-prompt detection, comprehensive intake questions asked one at a time, and LLM-decide logic. Never invoked directly; called by master and standalone domain commands. |
| type | shared |
This file is referenced by master.md and domain commands. Never invoke directly.
Count the words in $ARGUMENTS and scan for domain signals.
Rich prompt (skip all intake questions → proceed to execution):
Vague prompt (run intake): anything that doesn't meet rich-prompt criteria.
Even with a rich prompt, if --confirm flag is present: skip to execution but show the plan before spawning agents and wait for "go".
Ask ONE question at a time. Wait for the answer before asking the next. Stop asking as soon as you have enough to proceed.
Q1 — Goal:
"What outcome defines success for this run? Be as specific as you can — what will be done or produced when we're finished?"
Q2 — Scope:
"Which business domains should this touch? Options: build, idea, marketing, review, research, content, release, sales, ops, finance — or should I decide based on the goal?"
Q3 — Constraints:
"Any constraints I should know about? Examples: don't touch production, stay within this codebase, only content work this week, timeline by end of sprint."
Q4 — Mode:
"Should I execute automatically once I have a plan, or show you the plan first and wait for your approval before spawning agents?"
Q5 — Project:
"Which project is this for? I'll create or find a monotask space with that name. (Or I can infer it from context.)"
Skip Q4 if --auto or --confirm flag was provided. Skip Q5 if --project <name> flag was provided.
If the user responds with any of: "decide yourself", "you decide", "your call", "whatever you think", "up to you" — to any intake question:
"I'm choosing [X] because [one-sentence reason]."
confidence: 0.7 and outcome: pending.After intake (or skip), resolve the execution mode:
| Flag / Answer | Mode |
|---|---|
--auto flag | auto — spawn immediately after planning |
--confirm flag | confirm — show plan, wait for "go" |
| Q4 answer: "auto" or "yes go ahead" | auto |
| Q4 answer: "show me first" or "confirm" | confirm |
| No flag, vague prompt | confirm (default for vague) |
| No flag, rich prompt | auto (default for rich) |
Priority order:
--project <name> flag — use exactly as providedsession-YYYY-MM-DD