GemBoost Behavioral Modes Guide 🧠

✅ Quick Verification

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

Quick Reference Table

Mode	Purpose	Auto-Triggers	Key Behaviors	Best Used For
🧠 Brainstorming	Interactive discovery	"brainstorm", "maybe", vague requests	Socratic questions, requirement elicitation	New project planning, unclear requirements
🔍 Introspection	Meta-cognitive analysis	Error recovery, "analyze reasoning"	Transparent thinking markers (🤔, 🎯, 💡)	Debugging, learning, optimization
📋 Task Management	Complex coordination	>3 steps, >2 directories	Phase breakdown, memory persistence	Multi-step operations, project management
🎯 Orchestration	Intelligent tool selection	Multi-tool ops, high resource usage	Optimal tool routing, parallel execution	Complex analysis, performance optimization
⚡ Token Efficiency	Compressed communication	High context usage, `--uc` flag	Symbol systems, estimated 30-50% token reduction	Resource constraints, large operations

Getting Started (2-Minute Overview)

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

Quick Examples:

# Automatic activation examples
/gb:brainstorm "mobile app"        # → Socratic discovery questions
/gb: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: /gb: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 GemBoost 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

📋 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 Gemini 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
/gb:brainstorm "microservices architecture" --task-manage
# → Brainstorming: requirement discovery
# → Task Management: multi-phase coordination

# Analysis with transparency and efficiency
/gb: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
/gb:implement "user login" --brainstorm

# Add reasoning transparency to debugging
/gb:fix auth-issue --introspect

# Enable task management for simple operations
/gb:update styles.css --task-manage

Mode Boundaries and Priority

When Modes Activate:

Complexity Threshold: >3 files → Task Management
Resource Pressure: High context usage → Token Efficiency
Multi-Tool Need: Complex analysis → Orchestration
Uncertainty: Vague requirements → Brainstorming
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)
/gb:implement "core productivity features"
→ 📋 Multi-phase breakdown with dependencies
→ 🎯 Phase coordination with quality gates

# Phase 3: Implementation (Orchestration Mode coordinates tools)
/gb:develop frontend + backend
→ 🎯 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)
/gb:fix auth-system --comprehensive
→ 📋 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
/gb:modernize 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

Trigger Type	Example Input	Mode Activated	Key Behavior
Vague Request	"I want to build an app"	🧠 Brainstorming	Socratic discovery questions
Complex Scope	>3 files or >2 directories	📋 Task Management	Phase coordination
Multi-Tool Need	Analysis + Implementation	🎯 Orchestration	Tool optimization
Error Recovery	"This isn't working as expected"	🔍 Introspection	Transparent reasoning
Resource Pressure	High context usage	⚡ Token Efficiency	Symbol compression
Simple Task	"Fix this function"	🎨 Standard	Clear, direct approach

Manual Override Commands

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

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

Mode-Specific Troubleshooting

Brainstorming Mode Issues:

# Problem: Mode gives solutions instead of asking questions
# Quick Fix: Check request clarity and use explicit flag
/gb: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
/gb:implement "function" --no-task-manage     # Disable coordination
/gb:simple-fix 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
/gb:command --no-uc                           # Disable compression
/gb: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
/gb: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
/gb:command --no-mcp                          # Native tools only
/gb:command --simple                          # Basic execution
# Check if task complexity justifies orchestration

Error Code Reference

Mode Error	Meaning	Quick Fix
B001	Brainstorming failed to activate	Use explicit `--brainstorm` flag
T001	Task management overhead	Use `--no-task-manage` for simple tasks
U001	Token efficiency too aggressive	Use `--verbose` or `--no-uc`
I001	Introspection mode stuck	Use `--no-introspect` for direct action
O001	Orchestration coordination failed	Use `--no-mcp` or `--simple`
M001	Mode conflict detected	Check flag priority rules
M002	Mode switching loop	Restart session to reset state
M003	Mode not recognized	Update GemBoost or check spelling

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 Gemini Cli session

Level 2: Detailed Help (5-15 min)

# Mode-specific diagnostics
/gb:help modes                            # List all available modes
/gb: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
GemBoost 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:

/gb:command --brainstorm     # Force discovery
/gb:command --introspect     # Add transparency
/gb:command --task-manage    # Enable coordination
/gb: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

GemBoost'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 GemBoost automatically adapts its approach to match your needs.