SuperClaude/superclaude/core/BUSINESS_PANEL_EXAMPLES.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

8.1 KiB

BUSINESS_PANEL_EXAMPLES.md - Usage Examples and Integration Patterns

Basic Usage Examples

Example 1: Strategic Plan Analysis

/sc:business-panel @strategy_doc.pdf

# Output: Discussion mode with Porter, Collins, Meadows, Doumont
# Analysis focuses on competitive positioning, organizational capability, 
# system dynamics, and communication clarity

Example 2: Innovation Assessment

/sc:business-panel "We're developing AI-powered customer service" --experts "christensen,drucker,godin"

# Output: Discussion mode focusing on jobs-to-be-done, customer value, 
# and remarkability/tribe building

Example 3: Risk Analysis with Debate

/sc:business-panel @risk_assessment.md --mode debate

# Output: Debate mode with Taleb challenging conventional risk assessments,
# other experts defending their frameworks, systems perspective on conflicts

Example 4: Strategic Learning Session

/sc:business-panel "Help me understand competitive strategy" --mode socratic

# Output: Socratic mode with strategic questions from multiple frameworks,
# progressive questioning based on user responses

Advanced Usage Patterns

Multi-Document Analysis

/sc:business-panel @market_research.pdf @competitor_analysis.xlsx @financial_projections.csv --synthesis-only

# Comprehensive analysis across multiple documents with focus on synthesis

Domain-Specific Analysis

/sc:business-panel @product_strategy.md --focus "innovation" --experts "christensen,drucker,meadows"

# Innovation-focused analysis with disruption theory, management principles, systems thinking

Structured Communication Focus

/sc:business-panel @exec_presentation.pptx --focus "communication" --structured

# Analysis focused on message clarity, audience needs, cognitive load optimization

Integration with SuperClaude Commands

Combined with /analyze

/analyze @business_model.md --business-panel

# Technical analysis followed by business expert panel review

Combined with /improve

/improve @strategy_doc.md --business-panel --iterative

# Iterative improvement with business expert validation

Combined with /design

/design business-model --business-panel --experts "drucker,porter,kim_mauborgne"

# Business model design with expert guidance

Expert Selection Strategies

By Business Domain

strategy_planning:
  experts: ['porter', 'kim_mauborgne', 'collins', 'meadows']
  rationale: "Competitive analysis, blue ocean opportunities, execution excellence, systems thinking"

innovation_management:
  experts: ['christensen', 'drucker', 'godin', 'meadows']  
  rationale: "Disruption theory, systematic innovation, remarkability, systems approach"

organizational_development:
  experts: ['collins', 'drucker', 'meadows', 'doumont']
  rationale: "Excellence principles, management effectiveness, systems change, clear communication"

risk_management:
  experts: ['taleb', 'meadows', 'porter', 'collins']
  rationale: "Antifragility, systems resilience, competitive threats, disciplined execution"

market_entry:
  experts: ['porter', 'christensen', 'godin', 'kim_mauborgne']
  rationale: "Industry analysis, disruption potential, tribe building, blue ocean creation"

business_model_design:
  experts: ['christensen', 'drucker', 'kim_mauborgne', 'meadows']
  rationale: "Value creation, customer focus, value innovation, system dynamics"

By Analysis Type

comprehensive_audit:
  experts: "all"
  mode: "discussion → debate → synthesis"
  
strategic_validation:
  experts: ['porter', 'collins', 'taleb']
  mode: "debate"
  
learning_facilitation:
  experts: ['drucker', 'meadows', 'doumont']
  mode: "socratic"

quick_assessment:
  experts: "auto-select-3"
  mode: "discussion"
  flags: "--synthesis-only"

Output Format Variations

Executive Summary Format

/sc:business-panel @doc.pdf --structured --synthesis-only

# Output:
## 🎯 Strategic Assessment
**💰 Financial Impact**: [Key economic drivers]
**🏆 Competitive Position**: [Advantage analysis]  
**📈 Growth Opportunities**: [Expansion potential]
**⚠️ Risk Factors**: [Critical threats]
**🧩 Synthesis**: [Integrated recommendation]

Framework-by-Framework Format

/sc:business-panel @doc.pdf --verbose

# Output:
## 📚 CHRISTENSEN - Disruption Analysis
[Detailed jobs-to-be-done and disruption assessment]

## 📊 PORTER - Competitive Strategy  
[Five forces and value chain analysis]

## 🧩 Cross-Framework Synthesis
[Integration and strategic implications]

Question-Driven Format

/sc:business-panel @doc.pdf --questions

# Output:
## 🤔 Strategic Questions for Consideration
**🔨 Innovation Questions** (Christensen):
- What job is this being hired to do?

**⚔️ Competitive Questions** (Porter):  
- What are the sustainable advantages?

**🧭 Management Questions** (Drucker):
- What should our business be?

Integration Workflows

Business Strategy Development

workflow_stages:
  stage_1: "/sc:business-panel @market_research.pdf --mode discussion"
  stage_2: "/sc:business-panel @competitive_analysis.md --mode debate"  
  stage_3: "/sc:business-panel 'synthesize findings' --mode socratic"
  stage_4: "/design strategy --business-panel --experts 'porter,kim_mauborgne'"

Innovation Pipeline Assessment

workflow_stages:
  stage_1: "/sc:business-panel @innovation_portfolio.xlsx --focus innovation"
  stage_2: "/improve @product_roadmap.md --business-panel"
  stage_3: "/analyze @market_opportunities.pdf --business-panel --think"

Risk Management Review

workflow_stages:
  stage_1: "/sc:business-panel @risk_register.pdf --experts 'taleb,meadows,porter'"
  stage_2: "/sc:business-panel 'challenge risk assumptions' --mode debate"
  stage_3: "/implement risk_mitigation --business-panel --validate"

Customization Options

Expert Behavior Modification

# Focus specific expert on particular aspect
/sc:business-panel @doc.pdf --christensen-focus "disruption-potential"
/sc:business-panel @doc.pdf --porter-focus "competitive-moats"

# Adjust expert interaction style  
/sc:business-panel @doc.pdf --interaction "collaborative" # softer debate mode
/sc:business-panel @doc.pdf --interaction "challenging" # stronger debate mode

Output Customization

# Symbol density control
/sc:business-panel @doc.pdf --symbols minimal  # reduce symbol usage
/sc:business-panel @doc.pdf --symbols rich     # full symbol system

# Analysis depth control
/sc:business-panel @doc.pdf --depth surface    # high-level overview
/sc:business-panel @doc.pdf --depth detailed   # comprehensive analysis

Time and Resource Management

# Quick analysis for time constraints
/sc:business-panel @doc.pdf --quick --experts-max 3

# Comprehensive analysis for important decisions  
/sc:business-panel @doc.pdf --comprehensive --all-experts

# Resource-aware analysis
/sc:business-panel @doc.pdf --budget 10000  # token limit

Quality Validation

Analysis Quality Checks

authenticity_validation:
  voice_consistency: "Each expert maintains characteristic style"
  framework_fidelity: "Analysis follows authentic methodology"
  interaction_realism: "Expert dynamics reflect professional patterns"

business_relevance:
  strategic_focus: "Analysis addresses real strategic concerns"  
  actionable_insights: "Recommendations are implementable"
  evidence_based: "Conclusions supported by framework logic"

integration_quality:
  synthesis_value: "Combined insights exceed individual analysis"
  framework_preservation: "Integration maintains framework distinctiveness"
  practical_utility: "Results support strategic decision-making"

Performance Standards

response_time:
  simple_analysis: "< 30 seconds"
  comprehensive_analysis: "< 2 minutes"
  multi_document: "< 5 minutes"

token_efficiency:
  discussion_mode: "8-15K tokens"
  debate_mode: "10-20K tokens"  
  socratic_mode: "12-25K tokens"
  synthesis_only: "3-8K tokens"

accuracy_targets:
  framework_authenticity: "> 90%"
  strategic_relevance: "> 85%"
  actionable_insights: "> 80%"