SuperClaude Behavioral Modes Guide 🧠

✅ Quick Verification

Test modes by using /sc: commands - they activate automatically based on task complexity. For full command reference, see Commands Guide.

Quick Reference Table

Getting Started (2-Minute Overview)

Modes activate through behavioral instructions - Claude Code reads context files to determine which mode behaviors to adopt based on your task patterns and complexity.

Quick Examples:

# Automatic activation examples
/sc:brainstorm "mobile app"        # → Socratic discovery questions
/sc:implement "auth system"        # → Multi-phase coordination  
"--uc analyze large-codebase/"     # → Compressed symbol output

When to use manual flags:

• Need specific behavior: --brainstorm, --introspect, --uc
• Override automatic detection for learning/debugging
• Optimize for specific constraints (memory, time, clarity)

Mode Details

🧠 Brainstorming Mode - Interactive Discovery

Purpose: Transform vague ideas into structured requirements through collaborative discovery.

Auto-Activation Triggers:

• Vague project requests: "I want to build...", "Thinking about creating..."
• Exploration keywords: brainstorm, explore, discuss, figure out, not sure
• Uncertainty indicators: "maybe", "possibly", "could we"
• Manual flags: --brainstorm, --bs

Behavioral Changes:

• Socratic Questioning: Asks probing questions to uncover hidden requirements
• Non-Presumptive Approach: Avoids assumptions, lets you guide discovery direction
• Collaborative Partnership: Works with you in exploration rather than directive consultation
• Requirement Synthesis: Converts insights into structured technical briefs
• Cross-Session Memory: Maintains discovery context for follow-up discussions

Example Experience:

Standard Approach: "I'll build a user authentication system with JWT tokens..."
Brainstorming Approach: 
"🤔 Let's explore this together:
 - What specific user problems does auth solve for your app?
 - Who are your users and what's their technical comfort level?  
 - Any existing systems or social logins to integrate with?
 - What security/compliance requirements do you have?
 📝 Outcome: Detailed auth requirements brief ready for implementation"

Success Criteria

• Responds with questions instead of immediate solutions
• Questions explore user needs, technical constraints, and business goals
• Maintains collaborative tone throughout discovery process
• Produces structured requirements or technical brief as outcome

Verify: /sc:brainstorm "web app" should ask about users, features, technology
Test: Vague requests should trigger discovery questions, not assumptions
Check: Mode should persist across follow-up questions in same conversation

Works Best With:

• → Task Management: Requirements discovery → systematic implementation planning
• → Orchestration: Requirements clarity → optimal tool selection for implementation
• Manual Override: Use --brainstorm to force discovery even for "clear" requirements

🔍 Introspection Mode - Meta-Cognitive Analysis

Purpose: Expose reasoning process for learning optimization and transparent decision-making.

Auto-Activation Triggers:

• Self-analysis requests: "analyze my reasoning", "reflect on decision"
• Error recovery scenarios and unexpected results requiring investigation
• Complex problem solving with multiple viable approaches
• Pattern recognition needs for optimization opportunities
• Manual flag: --introspect

Behavioral Changes:

• Reasoning Transparency: Exposes thinking process with clear markers (🤔, 🎯, ⚡, 📊, 💡)
• Decision Analysis: Evaluates choice logic and considers alternative approaches
• Pattern Recognition: Identifies recurring behaviors and improvement opportunities
• Meta-Learning: Extracts insights for continuous framework improvement
• Framework Compliance: Validates actions against SuperClaude principles and quality gates

Example Experience:

Standard Approach: "I'll analyze this code structure and suggest improvements..."
Introspective Approach:
"🧠 Meta-Analysis: Why did I choose structural analysis over functional flow?
 🎯 Decision Logic: Saw class hierarchy → assumed OOP pattern dominance
 🔄 Alternative Considered: Data flow analysis might reveal hidden dependencies
 📊 Evidence Check: File imports suggest functional composition, not OOP
 💡 Learning: Need to analyze imports before choosing analysis strategy
 ⚡ Correction: Switching to functional flow analysis approach"

Works Best With:

• → Task Management: Provides transparent reasoning for complex phase decisions
• Any Mode: Adds reasoning transparency layer to any other mode's operation
• Manual Override: Use --introspect for learning sessions and debugging workflows

🔬 Deep Research Mode - Systematic Investigation Mindset

Purpose: Research mindset for systematic investigation and evidence-based reasoning.

Auto-Activation Triggers:

• /sc:research command invocation
• Research-related keywords: investigate, explore, discover, analyze
• Questions requiring current information beyond knowledge cutoff
• Complex research requirements
• Manual flag: --research

Behavioral Modifications:

• Thinking Style: Systematic over casual, evidence over assumption, progressive depth exploration
• Communication: Lead with confidence levels, provide inline citations, acknowledge uncertainties
• Priority Shifts: Completeness over speed, accuracy over speculation, verification over assumption
• Process Adaptations: Always create investigation plans, default to parallel operations, maintain evidence chains

6-Phase Research Workflow:

• 📋 Understand (5-10%): Assess query complexity and requirements
• 📝 Plan (10-15%): Select strategy (planning/intent/unified) and identify parallelization
• ✅ TodoWrite (5%): Create adaptive task hierarchy (3-15 tasks based on complexity)
• 🔄 Execute (50-60%): Parallel-first searches and smart extraction routing
• 📊 Track (Continuous): Monitor progress and update confidence scores
• ✓ Validate (10-15%): Verify evidence chains and ensure completeness

Example Experience:

Standard Mode: "Here are some search results about quantum computing..."
Deep Research Mode: 
"📊 Research Plan: Quantum computing breakthroughs
 ✓ TodoWrite: Created 8 research tasks
 🔄 Executing parallel searches across domains
 📈 Confidence: 0.82 across 15 verified sources
 📝 Report saved: docs/research/research_quantum_[timestamp].md"

Quality Standards

• Minimum 2 sources per claim with inline citations
• Confidence scoring (0.0-1.0) for all findings
• Parallel execution by default for independent operations
• Reports saved to docs/research/ with proper structure
• Clear methodology and evidence presentation

Verify: /sc:research "test topic" should create TodoWrite and execute systematically Test: All research should include confidence scores and citations Check: Reports should be saved to docs/research/ automatically

Works Best With:

• → Task Management: Research planning with TodoWrite integration
• → Orchestration: Parallel Tavily/Playwright coordination
• Manual Override: Use --depth and --strategy for fine control

📋 Task Management Mode - Complex Coordination

Purpose: Hierarchical task organization with session persistence for multi-step operations.

Auto-Activation Triggers:

• Operations requiring >3 coordinated steps
• Multiple file/directory scope (>2 directories OR >3 files)
• Complex dependencies requiring phases and checkpoints
• Quality improvement requests: polish, refine, enhance
• Manual flags: --task-manage, --delegate

Behavioral Changes:

• Hierarchical Planning: Breaks complex work into Plan → Phase → Task → Todo structure
• Session Persistence: Maintains project context and progress across interruptions
• Memory Integration: Uses write_memory/read_memory for state preservation
• Progress Orchestration: Coordinates TodoWrite with memory updates for tracking
• Quality Gates: Implements systematic validation checkpoints between phases

Example Experience:

Standard Approach: "I'll implement user authentication..." → Direct implementation
Task Management Approach:
"📋 Multi-Phase Implementation Plan:
 🎯 Phase 1: Security Requirements Analysis (Session 1)
 🎯 Phase 2: API Design & Documentation (Session 2)  
 🎯 Phase 3: Implementation & Testing (Session 3-4)
 🎯 Phase 4: Integration & Validation (Session 5)
 💾 Session persistence: Resume context automatically
 ✓ Quality gates: Validation before each phase transition"

Works Best With:

• Brainstorming →: Requirements discovery then systematic implementation
• + Orchestration: Task coordination with optimal tool selection
• + Introspection: Transparent reasoning for complex phase decisions

🎯 Orchestration Mode - Intelligent Tool Selection

Purpose: Optimize task execution through intelligent tool routing and parallel coordination.

Auto-Activation Triggers:

• Multi-tool operations requiring sophisticated coordination
• Performance constraints (high resource usage)
• Parallel execution opportunities (>3 independent files/operations)
• Complex routing decisions with multiple valid tool approaches

Behavioral Changes:

• Intelligent Tool Routing: Selects optimal MCP servers and native tools for each task type
• Resource Awareness: Adapts approach based on system constraints and availability
• Parallel Optimization: Identifies independent operations for concurrent execution
• Coordination Focus: Optimizes tool selection and usage through coordinated execution
• Adaptive Fallback: Switches tools gracefully when preferred options are unavailable

Example Experience:

Standard Approach: Sequential file-by-file analysis and editing
Orchestration Approach:
"🎯 Multi-Tool Coordination Strategy:
 🔍 Phase 1: Serena (semantic analysis) + Sequential (architecture review)
 ⚡ Phase 2: Morphllm (pattern edits) + Magic (UI components) 
 🧪 Phase 3: Playwright (testing) + Context7 (documentation patterns)
 🔄 Parallel execution: 3 tools working simultaneously
\"

Works Best With:

• Task Management →: Provides tool coordination for complex multi-phase plans
• + Token Efficiency: Optimal tool selection with compressed communication
• Any Complex Task: Adds intelligent tool routing to enhance execution

⚡ Token Efficiency Mode - Compressed Communication

Purpose: Achieve estimated 30-50% token reduction through symbol systems while preserving information quality.

Auto-Activation Triggers:

• High context usage approaching limits
• Large-scale operations requiring resource efficiency
• User explicit flags: --uc, --ultracompressed
• Complex analysis workflows with multiple outputs

Behavioral Changes:

• Symbol Communication: Uses visual symbols for logic flows, status, and technical domains
• Technical Abbreviation: Context-aware compression for repeated technical terms
• Structured Density: Bullet points, tables, and concise formatting over verbose paragraphs
• Information Preservation: Maintains ≥95% information quality despite compression
• Structured Format: Organized for clarity and task completion

Example Experience:

Standard Approach: "The authentication system implementation shows a security vulnerability in the user validation function that needs immediate attention..."
Token Efficient Approach:
"🛡️ Security Alert:
 auth.js:45 → user val() → critical vuln
 📊 Impact: ❌ token bypass possible
 ⚡ Action: fix validation + audit ∵ high sev
 🔧 Est: 2h impl + 1h test"

Works Best With:

• Any Mode: Adds compression layer while preserving mode-specific behaviors
• Orchestration →: Compressed tool coordination and status updates
• Manual Override: Use --uc when context pressure or efficiency is priority

🎨 Standard Mode - Balanced Default

Purpose: Provide clear, professional communication for straightforward development tasks.

Auto-Activation Triggers:

• Simple, well-defined tasks without complexity indicators
• Single-file operations with clear requirements
• Basic explanations and standard development workflows
• No other mode triggers detected (default fallback)

Behavioral Changes:

• Professional Communication: Clear, concise technical language without compression
• Moderate Detail: Balanced information depth suitable for most development tasks
• Standard Tool Selection: Uses native Claude capabilities and basic tools
• Quality Focus: Maintains code quality without complex orchestration overhead
• Responsive Adaptation: Ready to switch to specialized modes when complexity increases

Example Experience:

Standard Approach: Consistent, professional baseline for all tasks
"I'll implement the login function with proper error handling:
 
 1. Validate user input (email format, password requirements)
 2. Authenticate against database with secure hashing
 3. Generate JWT token with appropriate expiration
 4. Return success response with user data
 
 The implementation will follow security best practices and include comprehensive error handling."

Works Best With:

• → Any Mode: Serves as baseline that other modes enhance
• Mode Switching: Automatically escalates to specialized modes when needed
• Clarity Priority: When straightforward communication is more important than optimization

Advanced Usage

Mode Combinations

Multi-Mode Workflows:

# Discovery → Planning → Implementation
/sc:brainstorm "microservices architecture" --task-manage
# → Brainstorming: requirement discovery
# → Task Management: multi-phase coordination

# Analysis with transparency and efficiency
/sc:analyze legacy-system/ --introspect --uc
# → Introspection: transparent reasoning
# → Token Efficiency: compressed output

Manual Mode Control

Force Specific Behaviors:

• --brainstorm: Force collaborative discovery for any task
• --introspect: Add reasoning transparency to any mode
• --task-manage: Enable hierarchical coordination
• --orchestrate: Optimize tool selection and parallel execution
• --uc: Compress communication for efficiency

Override Examples:

# Force brainstorming on "clear" requirements
/sc:implement "user login" --brainstorm

# Add reasoning transparency to debugging
# Debug authentication issue with transparent reasoning

# Enable task management for simple operations
# Update styles.css with systematic task management

Mode Boundaries and Priority

When Modes Activate:

1. Complexity Threshold: >3 files → Task Management
2. Resource Pressure: High context usage → Token Efficiency
3. Multi-Tool Need: Complex analysis → Orchestration
4. Uncertainty: Vague requirements → Brainstorming
5. Error Recovery: Problems → Introspection

Priority Rules:

• Safety First: Quality and validation always override efficiency
• User Intent: Manual flags override automatic detection
• Context Adaptation: Modes stack based on complexity
• Resource Management: Efficiency modes activate under pressure

Real-World Examples

Complete Workflow Examples

New Project Development:

# Phase 1: Discovery (Brainstorming Mode auto-activates)
"I want to build a productivity app"
→ 🤔 Socratic questions about users, features, platform choice
→ 📝 Structured requirements brief

# Phase 2: Planning (Task Management Mode auto-activates)  
/sc:implement "core productivity features"
→ 📋 Multi-phase breakdown with dependencies
→ 🎯 Phase coordination with quality gates

# Phase 3: Implementation (Orchestration Mode coordinates tools)
/sc:implement "frontend and backend systems"
→ 🎯 Magic (UI) + Context7 (patterns) + Sequential (architecture)
→ ⚡ Parallel execution optimization

Debugging Complex Issues:

# Problem analysis (Introspection Mode auto-activates)
"Users getting intermittent auth failures"
→ 🤔 Transparent reasoning about potential causes
→ 🎯 Hypothesis formation and evidence gathering
→ 💡 Pattern recognition across similar issues

# Systematic resolution (Task Management coordinates)
# Fix authentication system comprehensively
→ 📋 Phase 1: Root cause analysis
→ 📋 Phase 2: Solution implementation  
→ 📋 Phase 3: Testing and validation

Mode Combination Patterns

High-Complexity Scenarios:

# Large refactoring with multiple constraints
/sc:improve legacy-system/ --introspect --uc --orchestrate
→ 🔍 Transparent reasoning (Introspection)
→ ⚡ Compressed communication (Token Efficiency)  
→ 🎯 Optimal tool coordination (Orchestration)
→ 📋 Systematic phases (Task Management auto-activates)

Quick Reference

Mode Activation Patterns

Manual Override Commands

# Force specific mode behaviors
/sc:command --brainstorm    # Collaborative discovery
/sc:command --introspect    # Reasoning transparency
/sc:command --task-manage   # Hierarchical coordination
/sc:command --orchestrate   # Tool optimization
/sc:command --uc           # Token compression

# Combine multiple modes
/sc:command --introspect --uc    # Transparent + efficient
/sc:command --task-manage --orchestrate  # Coordinated + optimized

Troubleshooting

For troubleshooting help, see:

• Common Issues - Quick fixes for frequent problems
• Troubleshooting Guide - Comprehensive problem resolution

Common Issues

• Mode not activating: Use manual flags: --brainstorm, --introspect, --uc
• Wrong mode active: Check complexity triggers and keywords in request
• Mode switching unexpectedly: Normal behavior based on task evolution
• Execution impact: Modes optimize tool usage, shouldn't affect execution
• Mode conflicts: Check flag priority rules in Flags Guide

Immediate Fixes

• Force specific mode: Use explicit flags like --brainstorm or --task-manage
• Reset mode behavior: Restart Claude Code session to reset mode state
• Check mode indicators: Look for 🤔, 🎯, 📋 symbols in responses
• Verify complexity: Simple tasks use Standard mode, complex tasks auto-switch

Mode-Specific Troubleshooting

Brainstorming Mode Issues:

# Problem: Mode gives solutions instead of asking questions
# Quick Fix: Check request clarity and use explicit flag
/sc:brainstorm "web app" --brainstorm         # Force discovery mode
"I have a vague idea about..."                # Use uncertainty language
"Maybe we could build..."                     # Trigger exploration

Task Management Mode Issues:

# Problem: Simple tasks getting complex coordination
# Quick Fix: Reduce scope or use simpler commands
/sc:implement "function" --no-task-manage     # Disable coordination
/sc:troubleshoot bug.js                       # Use basic commands
# Check if task really is complex (>3 files, >2 directories)

Token Efficiency Mode Issues:

# Problem: Output too compressed or unclear
# Quick Fix: Disable compression for clarity
/sc:command --no-uc                           # Disable compression
/sc:command --verbose                         # Force detailed output
# Use when clarity is more important than efficiency

Introspection Mode Issues:

# Problem: Too much meta-commentary, not enough action
# Quick Fix: Disable introspection for direct work
/sc:command --no-introspect                   # Direct execution
# Use introspection only for learning and debugging

Orchestration Mode Issues:

# Problem: Tool coordination causing confusion
# Quick Fix: Simplify tool usage
/sc:command --no-mcp                          # Native tools only
/sc:command --simple                          # Basic execution
# Check if task complexity justifies orchestration

Error Code Reference

Progressive Support Levels

Level 1: Quick Fix (< 2 min)

• Use manual flags to override automatic mode selection
• Check if task complexity matches expected mode behavior
• Try restarting Claude Code session

Level 2: Detailed Help (5-15 min)

# Mode-specific diagnostics
/sc:help modes                            # List all available modes
/sc:reflect --type mode-status            # Check current mode state
# Review request complexity and triggers

• See Common Issues Guide for mode installation problems

Level 3: Expert Support (30+ min)

# Deep mode analysis
SuperClaude install --diagnose
# Check mode activation patterns
# Review behavioral triggers and thresholds

• See Diagnostic Reference Guide for behavioral mode analysis

Level 4: Community Support

• Report mode issues at GitHub Issues
• Include examples of unexpected mode behavior
• Describe desired vs actual mode activation

Success Validation

After applying mode fixes, test with:

• Simple requests use Standard mode (clear, direct responses)
• Complex requests auto-activate appropriate modes (coordination, reasoning)
• Manual flags override automatic detection correctly
• Mode indicators (🤔, 🎯, 📋) appear when expected
• Performance remains good across different modes

Quick Troubleshooting (Legacy)

• Mode not activating → Use manual flags: --brainstorm, --introspect, --uc
• Wrong mode active → Check complexity triggers and keywords in request
• Mode switching unexpectedly → Normal behavior based on task evolution
• Execution impact → Modes optimize tool usage, shouldn't affect execution
• Mode conflicts → Check flag priority rules in Flags Guide

Frequently Asked Questions

Q: How do I know which mode is active? A: Look for these indicators in communication patterns:

• 🤔 Discovery questions → Brainstorming
• 🎯 Reasoning transparency → Introspection
• Phase breakdowns → Task Management
• Tool coordination → Orchestration
• Symbol compression → Token Efficiency

Q: Can I force specific modes? A: Yes, use manual flags to override automatic detection:

/sc:command --brainstorm     # Force discovery
/sc:command --introspect     # Add transparency
/sc:command --task-manage    # Enable coordination
/sc:command --uc            # Compress output

Q: Do modes affect execution? A: Modes optimize tool usage through coordination:

• Token Efficiency: 30-50% context reduction
• Orchestration: Parallel processing
• Task Management: Prevents rework through systematic planning

Q: Can modes work together? A: Yes, modes are designed to complement each other:

• Task Management coordinates other modes
• Token Efficiency compresses any mode's output
• Introspection adds transparency to any workflow

Summary

SuperClaude's 5 behavioral modes create an intelligent adaptation system that matches your needs automatically:

• 🧠 Brainstorming: Transforms vague ideas into clear requirements
• 🔍 Introspection: Provides transparent reasoning for learning and debugging
• 📋 Task Management: Coordinates complex multi-step operations
• 🎯 Orchestration: Optimizes tool selection and parallel execution
• ⚡ Token Efficiency: Compresses communication while preserving clarity
• 🎨 Standard: Maintains professional baseline for straightforward tasks

The key insight: You don't need to think about modes - they work transparently to enhance your development experience. Simply describe what you want to accomplish, and SuperClaude automatically adapts its approach to match your needs.

Related Guides

Learning Progression:

🌱 Essential (Week 1)

• Quick Start Guide - Mode activation examples
• Commands Reference - Commands automatically activate modes
• Installation Guide - Set up behavioral modes

🌿 Intermediate (Week 2-3)

• Agents Guide - How modes coordinate with specialists
• Flags Guide - Manual mode control and optimization
• Examples Cookbook - Mode patterns in practice

🌲 Advanced (Month 2+)

• MCP Servers - Mode integration with enhanced capabilities
• Session Management - Task Management mode workflows
• Getting Started - Mode usage patterns

🔧 Expert

• Technical Architecture - Mode implementation details
• Contributing Code - Extend mode capabilities

Mode-Specific Guides:

• Brainstorming: Requirements Discovery Patterns
• Task Management: Session Management Guide
• Orchestration: MCP Servers Guide
• Token Efficiency: Command Fundamentals