Agent Guides — скилл

---
description: Multi-specialist collaborative analysis — fans a topic out to parallel specialist subagents, cross-pollinates findings, and synthesizes across rounds
argument-hint: "<topic> [rounds=3]"
disable-model-invocation: true
---

# Multi-Mind - Subagent-Based Collaborative Analysis

Execute a multi-specialist collaborative analysis on: **$ARGUMENTS**

Parse an optional `rounds=N` parameter (default 3).

## How this maps to Claude Code's agent system

- Launch each specialist as a **parallel subagent** via the Task tool — they run concurrently, each in its own context window, and return only their analysis.
- For one-off runs, inline subagent prompts (below) are enough. For topics you revisit, make the specialists persistent by writing definitions to `.claude/agents/<role>.md` (see the [Subagents Guide](../claude-subagents-guide.md)) — Claude will then route to them by description automatically.
- Subagents run in the background by default; launch all specialists for a round in a single message so they execute in parallel.
- If the question needs codebase-wide changes (not just analysis), the bundled `/batch` skill is a better fit. For long-running collaborative sessions, see agent teams in the Claude Code docs.

**When to use this vs. `/deep-research`:** the bundled `/deep-research` workflow fans out web searches and synthesizes a cited report — use it for factual questions. Use multi-mind for *judgment* questions (architecture tradeoffs, strategy, design decisions) where decorrelated expert perspectives and adversarial cross-pollination matter more than citation coverage.

## Phase 1: Specialist Assignment & Research

Analyze the topic and determine 4-6 specialist roles with maximally decorrelated perspectives. Then launch them all in parallel, e.g.:

```
Task tool, subagent_type: general-purpose — run all in one block:

1. "You are a technical specialist. Research [topic] focusing on implementation
   details, architecture, performance, and technical risk. Use web search for
   current documentation and case studies. Return ≤500 words of findings."

2. "You are a business strategy specialist. Analyze [topic] from market dynamics,
   competitive landscape, ROI, and strategic positioning. Use web search for
   current market reports. Return ≤500 words."

3. "You are a user experience / adoption specialist. Investigate [topic] for
   user needs, usability concerns, and adoption barriers. Return ≤500 words."

[... additional specialists as the topic demands — security, regulatory,
 ethics, operations, contrarian/red-team ...]
```

**Specialist selection criteria**:
- Unique domain expertise relevant to the topic