/consult-claude

name: multi-ai-consultant:consult-claude
description: Consult fresh Claude subagent for unbiased perspective on code problems. Use when stuck in mental rut, need quick second opinion, or want free alternative to external AIs.
allowed-tools:
  - Task
  - Read

Consult Fresh Claude

You are being asked to consult a fresh Claude subagent for a second opinion on a coding problem or architectural decision.

**Why this is useful**: You (the current Claude instance) may have accumulated context biases or locked into a particular approach. A fresh Claude subagent has no conversation history and can provide an unbiased perspective.

Your Task

1. **Gather Context**: Read relevant files for the problem 2. **Build Prompt**: Create a clear, specific question with context 3. **Launch Subagent**: Use Task tool with general-purpose subagent 4. **Receive Analysis**: Get fresh perspective from subagent 5. **Synthesize**: Compare subagent's analysis with your own reasoning 6. **Present**: Show 5-part synthesis to user 7. **Log Consultation**: Track usage (free, but still log)

---

Step 1: Gather Context

**You must read relevant files** before launching subagent. The subagent will NOT have access to your conversation history.

// Use Read tool to gather context
// For bug: Read the buggy file + related imports
// For architecture: Read key files in the area of concern

**Context to gather**:

• The file(s) with the bug or architectural concern
• Related files (imports, dependencies)
• Error messages or logs
• Relevant documentation

**Store context in your working memory** - you'll pass it to the subagent in the prompt.

---

Step 2: Build Prompt

The prompt must include: 1. **Role**: Tell subagent they're providing a second opinion 2. **Problem statement**: What's wrong or what decision is needed 3. **Question**: Specific question for subagent 4. **Context**: Paste relevant code/files inline 5. **Your analysis**: What the primary Claude instance has tried 6. **Instructions**: Ask for specific format

**Format**:

You are providing a second opinion to another Claude Code instance that is stuck on a problem.

Problem: [Brief description]
Question: [Specific question]

Primary Claude's analysis:
- Tried: [What was attempted]
- Current status: [What's happening]
- Hypothesis: [What primary Claude thinks]

Context:

```[language]
[Paste relevant code here]

[Additional files or context as needed]

Your task: 1. Analyze the problem with fresh eyes 2. Identify what might have been missed 3. Propose solutions 4. Explain your reasoning 5. Note any risks or trade-offs

---

## Step 3: Launch Subagent

Use the **Task tool** with `subagent_type: "general-purpose"`.

```typescript
// Example invocation
Task({
  subagent_type: "general-purpose",
  description: "Fresh perspective on [bug|architecture]",
  prompt: `[Your formatted prompt from Step 2]`
})

**Important**:

• Use `general-purpose` subagent (has all tools)
• Keep prompt focused (don't overwhelm with context)
• Ask for specific deliverables
• Give subagent permission to use tools (Read, Grep, etc.) if needed

---

Step 4: Receive Analysis

The subagent will return a final message with their analysis.

**What to expect**:

• Fresh perspective (no conversation bias)
• May catch things you missed
• May validate your approach
• May suggest completely different direction

**Remember**: The subagent is equally capable but has different context. Neither of you is "right" by default.

---

Step 5: Synthesize (5-Part Format)

You MUST compare the subagent's analysis with your own reasoning. DO NOT just parrot the subagent's response.

**Required sections**:

🤖 My Analysis

• Your original reasoning
• What you tried
• What you think the issue is
• Your proposed solution
• Why you got stuck

🔄 Fresh Claude's Analysis

• Subagent's complete response
• Their reasoning
• What they identified
• Their proposed solution

🔍 Key Differences

• **Agreement**: Where you and subagent align
• **Divergence**: Where you disagree (explain why)
• **Fresh perspective value**: What did fresh eyes catch?
• **Context advantage**: What did your conversation history help with?
• **Blind spots**: What did each of you miss?

⚡ Synthesis

• Combine both perspectives
• Identify root cause (if bug)
• Weigh trade-offs (if architecture)
• Note any conflicting advice and why
• Determine which approach is better (or hybrid)

✅ Recommended Action

• Specific, actionable next steps
• File paths and line numbers
• Expected outcome
• Risk assessment
• Why this approach was chosen over alternatives

**End with**: "Should I proceed with this approach?"

---

Step 6: Log Consultation

# Create log directory if needed
mkdir -p ~/.claude/ai-consultations

# Log consultation (no cost, but track usage)
echo "$(date -Iseconds),claude-subagent,claude-sonnet-4-5,0,0,0.00,$(pwd)" \
  >> ~/.claude/ai-consultations/consultations.log

**Note**: Claude subagents are free (same API call), but we log them to track consultation patterns.

---

Context Management

**Advantages of Claude subagent**:

• ✅ Free (no additional API cost)
• ✅ Same capabilities as you
• ✅ Can use all tools (Read, Grep, Edit, etc.)
• ✅ Fresh perspective (no conversation bias)
• ✅ Fast (no external API calls)

**Limitations**:

• ❌ No web search (unlike Gemini)
• ❌ No extended thinking mode
• ❌ No grounding/verification
• ❌ Limited by same knowledge cutoff

**When to use Claude subagent**:

• Need fresh eyes on familiar code
• Stuck in a mental rut
• Want quick second opinion
• No need for web research
• Budget-conscious (free)

---

Example Usage

**Scenario**: State management bug in React app

**Your situation**:

• You've tried 3 different approaches
• Each fix causes new issues
• Convinced the problem is in useEffect
• Spent 20 minutes debugging

**Prompt to subagent**:

You are providing a second opinion to another Claude Code instance stuck on a Re