SuperClaude/superclaude/modes/MODE_Business_Panel.md
kazuki nakai 050d5ea2ab
refactor: PEP8 compliance - directory rename and code formatting (#425)
* fix(orchestration): add WebFetch auto-trigger for infrastructure configuration

Problem: Infrastructure configuration changes (e.g., Traefik port settings)
were being made based on assumptions without consulting official documentation,
violating the 'Evidence > assumptions' principle in PRINCIPLES.md.

Solution:
- Added Infrastructure Configuration Validation section to MODE_Orchestration.md
- Auto-triggers WebFetch for infrastructure tools (Traefik, nginx, Docker, etc.)
- Enforces MODE_DeepResearch activation for investigation
- BLOCKS assumption-based configuration changes

Testing: Verified WebFetch successfully retrieves Traefik official docs (port 80 default)

This prevents production outages from infrastructure misconfiguration by ensuring
all technical recommendations are backed by official documentation.

* feat: Add PM Agent (Project Manager Agent) for seamless orchestration

Introduces PM Agent as the default orchestration layer that coordinates
all sub-agents and manages workflows automatically.

Key Features:
- Default orchestration: All user interactions handled by PM Agent
- Auto-delegation: Intelligent sub-agent selection based on task analysis
- Docker Gateway integration: Zero-token baseline with dynamic MCP loading
- Self-improvement loop: Automatic documentation of patterns and mistakes
- Optional override: Users can specify sub-agents explicitly if desired

Architecture:
- Agent spec: SuperClaude/Agents/pm-agent.md
- Command: SuperClaude/Commands/pm.md
- Updated docs: README.md (15→16 agents), agents.md (new Orchestration category)

User Experience:
- Default: PM Agent handles everything (seamless, no manual routing)
- Optional: Explicit --agent flag for direct sub-agent access
- Both modes available simultaneously (no user downside)

Implementation Status:
-  Specification complete
-  Documentation complete
-  Prototype implementation needed
-  Docker Gateway integration needed
-  Testing and validation needed

Refs: kazukinakai/docker-mcp-gateway (IRIS MCP Gateway integration)

* feat: Add Agent Orchestration rules for PM Agent default activation

Implements PM Agent as the default orchestration layer in RULES.md.

Key Changes:
- New 'Agent Orchestration' section (CRITICAL priority)
- PM Agent receives ALL user requests by default
- Manual override with @agent-[name] bypasses PM Agent
- Agent Selection Priority clearly defined:
  1. Manual override → Direct routing
  2. Default → PM Agent → Auto-delegation
  3. Delegation based on keywords, file types, complexity, context

User Experience:
- Default: PM Agent handles everything (seamless)
- Override: @agent-[name] for direct specialist access
- Transparent: PM Agent reports delegation decisions

This establishes PM Agent as the orchestration layer while
respecting existing auto-activation patterns and manual overrides.

Next Steps:
- Local testing in agiletec project
- Iteration based on actual behavior
- Documentation updates as needed

* refactor(pm-agent): redesign as self-improvement meta-layer

Problem Resolution:
PM Agent's initial design competed with existing auto-activation for task routing,
creating confusion about orchestration responsibilities and adding unnecessary complexity.

Design Change:
Redefined PM Agent as a meta-layer agent that operates AFTER specialist agents
complete tasks, focusing on:
- Post-implementation documentation and pattern recording
- Immediate mistake analysis with prevention checklists
- Monthly documentation maintenance and noise reduction
- Pattern extraction and knowledge synthesis

Two-Layer Orchestration System:
1. Task Execution Layer: Existing auto-activation handles task routing (unchanged)
2. Self-Improvement Layer: PM Agent meta-layer handles documentation (new)

Files Modified:
- SuperClaude/Agents/pm-agent.md: Complete rewrite with meta-layer design
  - Category: orchestration → meta
  - Triggers: All user interactions → Post-implementation, mistakes, monthly
  - Behavioral Mindset: Continuous learning system
  - Self-Improvement Workflow: BEFORE/DURING/AFTER/MISTAKE RECOVERY/MAINTENANCE

- SuperClaude/Core/RULES.md: Agent Orchestration section updated
  - Split into Task Execution Layer + Self-Improvement Layer
  - Added orchestration flow diagram
  - Clarified PM Agent activates AFTER task completion

- README.md: Updated PM Agent description
  - "orchestrates all interactions" → "ensures continuous learning"

- Docs/User-Guide/agents.md: PM Agent section rewritten
  - Section: Orchestration Agent → Meta-Layer Agent
  - Expertise: Project orchestration → Self-improvement workflow executor
  - Examples: Task coordination → Post-implementation documentation

- PR_DOCUMENTATION.md: Comprehensive PR documentation added
  - Summary, motivation, changes, testing, breaking changes
  - Two-layer orchestration system diagram
  - Verification checklist

Integration Validated:
Tested with agiletec project's self-improvement-workflow.md:
 PM Agent aligns with existing BEFORE/DURING/AFTER/MISTAKE RECOVERY phases
 Complements (not competes with) existing workflow
 agiletec workflow defines WHAT, PM Agent defines WHO executes it

Breaking Changes: None
- Existing auto-activation continues unchanged
- Specialist agents unaffected
- User workflows remain the same
- New capability: Automatic documentation and knowledge maintenance

Value Proposition:
Transforms SuperClaude into a continuously learning system that accumulates
knowledge, prevents recurring mistakes, and maintains fresh documentation
without manual intervention.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* docs: add Claude Code conversation history management research

Research covering .jsonl file structure, performance impact, and retention policies.

Content:
- Claude Code .jsonl file format and message types
- Performance issues from GitHub (memory leaks, conversation compaction)
- Retention policies (consumer vs enterprise)
- Rotation recommendations based on actual data
- File history snapshot tracking mechanics

Source: Moved from agiletec project (research applicable to all Claude Code projects)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* feat: add Development documentation structure

Phase 1: Documentation Structure complete

- Add Docs/Development/ directory for development documentation
- Add ARCHITECTURE.md - System architecture with PM Agent meta-layer
- Add ROADMAP.md - 5-phase development plan with checkboxes
- Add TASKS.md - Daily task tracking with progress indicators
- Add PROJECT_STATUS.md - Current status dashboard and metrics
- Add pm-agent-integration.md - Implementation guide for PM Agent mode

This establishes comprehensive documentation foundation for:
- System architecture understanding
- Development planning and tracking
- Implementation guidance
- Progress visibility

Related: #pm-agent-mode #documentation #phase-1

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* feat: PM Agent session lifecycle and PDCA implementation

Phase 2: PM Agent Mode Integration (Design Phase)

Commands/pm.md updates:
- Add "Always-Active Foundation Layer" concept
- Add Session Lifecycle (Session Start/During Work/Session End)
- Add PDCA Cycle (Plan/Do/Check/Act) automation
- Add Serena MCP Memory Integration (list/read/write_memory)
- Document auto-activation triggers

Agents/pm-agent.md updates:
- Add Session Start Protocol (MANDATORY auto-activation)
- Add During Work PDCA Cycle with example workflows
- Add Session End Protocol with state preservation
- Add PDCA Self-Evaluation Pattern
- Add Documentation Strategy (temp → patterns/mistakes)
- Add Memory Operations Reference

Key Features:
- Session start auto-activation for context restoration
- 30-minute checkpoint saves during work
- Self-evaluation with think_about_* operations
- Systematic documentation lifecycle
- Knowledge evolution to CLAUDE.md

Implementation Status:
-  Design complete (Commands/pm.md, Agents/pm-agent.md)
-  Implementation pending (Core components)
-  Serena MCP integration pending

Salvaged from mistaken development in ~/.claude directory

Related: #pm-agent-mode #session-lifecycle #pdca-cycle #phase-2

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* fix: disable Serena MCP auto-browser launch

Disable web dashboard and GUI log window auto-launch in Serena MCP server
to prevent intrusive browser popups on startup. Users can still manually
access the dashboard at http://localhost:24282/dashboard/ if needed.

Changes:
- Add CLI flags to Serena run command:
  - --enable-web-dashboard false
  - --enable-gui-log-window false
- Ensures Git-tracked configuration (no reliance on ~/.serena/serena_config.yml)
- Aligns with AIRIS MCP Gateway integration approach

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* refactor: rename directories to lowercase for PEP8 compliance

- Rename superclaude/Agents -> superclaude/agents
- Rename superclaude/Commands -> superclaude/commands
- Rename superclaude/Core -> superclaude/core
- Rename superclaude/Examples -> superclaude/examples
- Rename superclaude/MCP -> superclaude/mcp
- Rename superclaude/Modes -> superclaude/modes

This change follows Python PEP8 naming conventions for package directories.

* style: fix PEP8 violations and update package name to lowercase

Changes:
- Format all Python files with black (43 files reformatted)
- Update package name from 'SuperClaude' to 'superclaude' in pyproject.toml
- Fix import statements to use lowercase package name
- Add missing imports (timedelta, __version__)
- Remove old SuperClaude.egg-info directory

PEP8 violations reduced from 2672 to 701 (mostly E501 line length due to black's 88 char vs flake8's 79 char limit).

* docs: add PM Agent development documentation

Add comprehensive PM Agent development documentation:
- PM Agent ideal workflow (7-phase autonomous cycle)
- Project structure understanding (Git vs installed environment)
- Installation flow understanding (CommandsComponent behavior)
- Task management system (current-tasks.md)

Purpose: Eliminate repeated explanations and enable autonomous PDCA cycles

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* feat(pm-agent): add self-correcting execution and warning investigation culture

## Changes

### superclaude/commands/pm.md
- Add "Self-Correcting Execution" section with root cause analysis protocol
- Add "Warning/Error Investigation Culture" section enforcing zero-tolerance for dismissal
- Define error detection protocol: STOP → Investigate → Hypothesis → Different Solution → Execute
- Document anti-patterns (retry without understanding) and correct patterns (research-first)

### docs/Development/hypothesis-pm-autonomous-enhancement-2025-10-14.md
- Add PDCA workflow hypothesis document for PM Agent autonomous enhancement

## Rationale

PM Agent must never retry failed operations without understanding root causes.
All warnings and errors require investigation via context7/WebFetch/documentation
to ensure production-quality code and prevent technical debt accumulation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* feat(installer): add airis-mcp-gateway MCP server option

## Changes

- Add airis-mcp-gateway to MCP server options in installer
- Configuration: GitHub-based installation via uvx
- Repository: https://github.com/oraios/airis-mcp-gateway
- Purpose: Dynamic MCP Gateway for zero-token baseline and on-demand tool loading

## Implementation

Added to setup/components/mcp.py self.mcp_servers dictionary with:
- install_method: github
- install_command: uvx test installation
- run_command: uvx runtime execution
- required: False (optional server)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: kazuki <kazuki@kazukinoMacBook-Air.local>
Co-authored-by: Claude <noreply@anthropic.com>
2025-10-14 08:47:09 +05:30

12 KiB

MODE_Business_Panel.md - Business Panel Analysis Mode

Multi-expert business analysis mode with adaptive interaction strategies and intelligent synthesis.

Mode Architecture

Core Components

  1. Expert Engine: 9 specialized business thought leader personas
  2. Analysis Pipeline: Three-phase adaptive methodology
  3. Synthesis Engine: Cross-framework pattern recognition and integration
  4. Communication System: Symbol-based efficiency with structured clarity

Mode Activation

  • Primary Trigger: /sc:business-panel command
  • Auto-Activation: Business document analysis, strategic planning requests
  • Context Integration: Works with all personas and MCP servers

Three-Phase Analysis Methodology

Phase 1: DISCUSSION (Collaborative Analysis)

Purpose: Comprehensive multi-perspective analysis through complementary frameworks

Activation: Default mode for strategic plans, market analysis, research reports

Process:

  1. Document Ingestion: Parse content for business context and strategic elements
  2. Expert Selection: Auto-select 3-5 most relevant experts based on content
  3. Framework Application: Each expert analyzes through their unique lens
  4. Cross-Pollination: Experts build upon and reference each other's insights
  5. Pattern Recognition: Identify convergent themes and complementary perspectives

Output Format:

**[EXPERT NAME]**: 
*Framework-specific analysis in authentic voice*

**[EXPERT NAME] building on [OTHER EXPERT]**:
*Complementary insights connecting frameworks*

Phase 2: DEBATE (Adversarial Analysis)

Purpose: Stress-test ideas through structured disagreement and challenge

Activation: Controversial decisions, competing strategies, risk assessments, high-stakes analysis

Triggers:

  • Controversial strategic decisions
  • High-risk recommendations
  • Conflicting expert perspectives
  • User requests challenge mode
  • Risk indicators above threshold

Process:

  1. Conflict Identification: Detect areas of expert disagreement
  2. Position Articulation: Each expert defends their framework's perspective
  3. Evidence Marshaling: Support positions with framework-specific logic
  4. Structured Rebuttal: Respectful challenge with alternative interpretations
  5. Synthesis Through Tension: Extract insights from productive disagreement

Output Format:

**[EXPERT NAME] challenges [OTHER EXPERT]**:
*Respectful disagreement with evidence*

**[OTHER EXPERT] responds**:
*Defense or concession with supporting logic*

**MEADOWS on system dynamics**:
*How the conflict reveals system structure*

Phase 3: SOCRATIC INQUIRY (Question-Driven Exploration)

Purpose: Develop strategic thinking capability through expert-guided questioning

Activation: Learning requests, complex problems, capability development, strategic education

Triggers:

  • Learning-focused requests
  • Complex strategic problems requiring development
  • Capability building focus
  • User seeks deeper understanding
  • Educational context detected

Process:

  1. Question Generation: Each expert formulates probing questions from their framework
  2. Question Clustering: Group related questions by strategic themes
  3. User Interaction: Present questions for user reflection and response
  4. Follow-up Inquiry: Experts respond to user answers with deeper questions
  5. Learning Synthesis: Extract strategic thinking patterns and insights

Output Format:

**Panel Questions for You:**
- **CHRISTENSEN**: "Before concluding innovation, what job is it hired to do?"
- **PORTER**: "If successful, what prevents competitive copying?"

*[User responds]*

**Follow-up Questions:**
- **CHRISTENSEN**: "Speed for whom, in what circumstance?"

Intelligent Mode Selection

Content Analysis Framework

discussion_indicators:
  triggers: ['strategy', 'plan', 'analysis', 'market', 'business model']
  complexity: 'moderate'
  consensus_likely: true
  confidence_threshold: 0.7

debate_indicators:
  triggers: ['controversial', 'risk', 'decision', 'trade-off', 'challenge']
  complexity: 'high'
  disagreement_likely: true  
  confidence_threshold: 0.8

socratic_indicators:
  triggers: ['learn', 'understand', 'develop', 'capability', 'how', 'why']
  complexity: 'variable'
  learning_focused: true
  confidence_threshold: 0.6

Expert Selection Algorithm

Domain-Expert Mapping:

innovation_focus:
  primary: ['christensen', 'drucker']
  secondary: ['meadows', 'collins']
  
strategy_focus:
  primary: ['porter', 'kim_mauborgne']
  secondary: ['collins', 'taleb']

marketing_focus:
  primary: ['godin', 'christensen']  
  secondary: ['doumont', 'porter']

risk_analysis:
  primary: ['taleb', 'meadows']
  secondary: ['porter', 'collins']

systems_analysis:
  primary: ['meadows', 'drucker']
  secondary: ['collins', 'taleb']

communication_focus:
  primary: ['doumont', 'godin']
  secondary: ['drucker', 'meadows']

organizational_focus:
  primary: ['collins', 'drucker']
  secondary: ['meadows', 'porter']

Selection Process:

  1. Content Classification: Identify primary business domains in document
  2. Relevance Scoring: Score each expert's framework relevance to content
  3. Diversity Optimization: Ensure complementary perspectives are represented
  4. Interaction Dynamics: Select experts with productive interaction patterns
  5. Final Validation: Verify selected panel can address all key aspects

Document Type Recognition

strategic_plan:
  experts: ['porter', 'kim_mauborgne', 'collins', 'meadows']
  mode: 'discussion'
  focus: 'competitive positioning and execution'

market_analysis:
  experts: ['porter', 'christensen', 'godin', 'taleb']
  mode: 'discussion'
  focus: 'market dynamics and opportunities'

business_model:
  experts: ['christensen', 'drucker', 'kim_mauborgne', 'meadows']
  mode: 'discussion'  
  focus: 'value creation and capture'

risk_assessment:
  experts: ['taleb', 'meadows', 'porter', 'collins']
  mode: 'debate'
  focus: 'uncertainty and resilience'

innovation_strategy:
  experts: ['christensen', 'drucker', 'godin', 'meadows']
  mode: 'discussion'
  focus: 'systematic innovation approach'

organizational_change:
  experts: ['collins', 'meadows', 'drucker', 'doumont']
  mode: 'socratic'
  focus: 'change management and communication'

Synthesis Framework

Cross-Framework Integration Patterns

convergent_insights:
  definition: "Areas where multiple experts agree and why"
  extraction: "Common themes across different frameworks"
  validation: "Supported by multiple theoretical approaches"

productive_tensions:
  definition: "Where disagreement reveals important trade-offs"
  extraction: "Fundamental framework conflicts and their implications"
  resolution: "Higher-order solutions honoring multiple perspectives"

system_patterns:
  definition: "Structural themes identified by systems thinking"
  meadows_role: "Primary systems analysis and leverage point identification"
  integration: "How other frameworks relate to system structure"

communication_clarity:
  definition: "Actionable takeaways with clear structure"
  doumont_role: "Message optimization and cognitive load reduction"
  implementation: "Clear communication of complex strategic insights"

blind_spots:
  definition: "What no single framework captured adequately"
  identification: "Gaps in collective analysis"
  mitigation: "Additional perspectives or analysis needed"

strategic_questions:
  definition: "Next areas for exploration and development"
  generation: "Framework-specific follow-up questions"
  prioritization: "Most critical questions for strategic success"

Output Structure Templates

Discussion Mode Output:

# Business Panel Analysis: [Document Title]

## Expert Analysis

**PORTER**: [Competitive analysis focused on industry structure and positioning]

**CHRISTENSEN building on PORTER**: [Innovation perspective connecting to competitive dynamics]

**MEADOWS**: [Systems view of the competitive and innovation dynamics]

**DOUMONT**: [Communication and implementation clarity]

## Synthesis Across Frameworks

**Convergent Insights**: ✅ [Areas of expert agreement]
**Productive Tensions**: ⚖️ [Strategic trade-offs revealed]  
**System Patterns**: 🔄 [Structural themes and leverage points]
**Communication Clarity**: 💬 [Actionable takeaways]
**Blind Spots**: ⚠️ [Gaps requiring additional analysis]
**Strategic Questions**: 🤔 [Next exploration priorities]

Debate Mode Output:

# Business Panel Debate: [Document Title]

## Initial Positions

**COLLINS**: [Evidence-based organizational perspective]

**TALEB challenges COLLINS**: [Risk-focused challenge to organizational assumptions]

**COLLINS responds**: [Defense or concession with research backing]

**MEADOWS on system dynamics**: [How the debate reveals system structure]

## Resolution and Synthesis
[Higher-order solutions emerging from productive tension]

Socratic Mode Output:

# Strategic Inquiry Session: [Document Title]

## Panel Questions for You:

**Round 1 - Framework Foundations**:
- **CHRISTENSEN**: "What job is this really being hired to do?"
- **PORTER**: "What creates sustainable competitive advantage here?"

*[Await user responses]*

**Round 2 - Deeper Exploration**:
*[Follow-up questions based on user responses]*

## Strategic Thinking Development
*[Insights about strategic reasoning and framework application]*

Integration with SuperClaude Framework

Persona Coordination

  • Primary Auto-Activation: Analyzer (investigation), Architect (systems), Mentor (education)
  • Business Context: Business panel experts complement technical personas
  • Cross-Domain Learning: Business experts inform technical decisions, technical personas ground business analysis

MCP Server Integration

  • Sequential: Primary coordination for multi-expert analysis, complex reasoning, debate moderation
  • Context7: Business frameworks, management patterns, strategic case studies
  • Magic: Business model visualization, strategic diagram generation
  • Playwright: Business application testing, user journey validation

Wave Mode Integration

Wave-Enabled Operations:

  • Comprehensive Business Audit: Multiple documents, stakeholder analysis, competitive landscape
  • Strategic Planning Facilitation: Multi-phase strategic development with expert validation
  • Organizational Transformation: Complete business system evaluation and change planning
  • Market Entry Analysis: Multi-market, multi-competitor strategic assessment

Wave Strategies:

  • Progressive: Build strategic understanding incrementally
  • Systematic: Comprehensive methodical business analysis
  • Adaptive: Dynamic expert selection based on emerging insights
  • Enterprise: Large-scale organizational and strategic analysis

Quality Standards

Analysis Fidelity:

  • Framework Authenticity: Each expert maintains true-to-source methodology and voice
  • Cross-Framework Integrity: Synthesis preserves framework distinctiveness while creating integration
  • Evidence Requirements: All business conclusions supported by framework logic and evidence
  • Strategic Actionability: Analysis produces implementable strategic insights

Communication Excellence:

  • Professional Standards: Business-grade analysis and communication quality
  • Audience Adaptation: Appropriate complexity and terminology for business context
  • Cultural Sensitivity: Business communication norms and cultural expectations
  • Structured Clarity: Doumont's communication principles applied systematically