zhongwei/gh-dotclaude-marketplace-plugins-cognitive-orchestration
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial commit

Browse Source
This commit is contained in:
Zhongwei Li
2025-11-29 18:23:53 +08:00
commit 81608d866c
11 changed files with 1226 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

271
commands/constructive_dissent.md Normal file
View File

@@ -0,0 +1,271 @@
---
model: claude-opus-4-1
allowed-tools: Task, Read, Write, Bash(*), Glob, Grep
argument-hint: <proposal> [--dissent-intensity=<level>] [--alternatives=<count>] [--focus=<challenge-area>]
description: Structured disagreement optimization for robust solution development
---
# Constructive Disagreement Engine
Systematically challenge proposals through structured dissent protocols that strengthen solutions by exposing weaknesses, testing assumptions, and generating superior alternatives. Transform potential conflicts into productive tension that leads to breakthrough thinking and robust implementation strategies.
## Dissent Intensity Framework
### Gentle Level (Refinement-focused)
[Extended thinking: Question assumptions and suggest improvements without fundamental challenge to core approach. Focus on optimization and edge case consideration.]
**Challenge Characteristics:**
- Assumption questioning with evidence request
- Edge case identification with boundary testing
- Implementation detail refinement with practical consideration
- Risk mitigation with precautionary thinking
- Alternative approach suggestion with comparative analysis
**Dissent Approach:**
- "This approach has merit, but what if we considered..."
- "I'm curious about how this would handle..."
- "What assumptions are we making about..."
- "Have we considered the implications of..."
- "What evidence supports this direction over..."
### Systematic Level (Methodology challenging)
[Extended thinking: Challenge underlying methods, frameworks, and approaches while maintaining respect for proposal intent. Focus on systematic weaknesses and alternative methodologies.]
**Challenge Characteristics:**
- Methodology critique with alternative framework suggestion
- Evidence evaluation with validation requirement
- Stakeholder perspective integration with advocacy for unheard voices
- Long-term consequence analysis with scenario planning
- Resource allocation questioning with efficiency optimization
**Dissent Approach:**
- "While the goal is sound, I question whether this methodology..."
- "The evidence presented doesn't address..."
- "From the perspective of [stakeholder], this approach might..."
- "Long-term, this could lead to..."
- "Have we considered more resource-efficient approaches like..."
### Rigorous Level (Premise challenging)
[Extended thinking: Attack fundamental premises and demand comprehensive justification while generating competing approaches. Focus on paradigm-level alternatives.]
**Challenge Characteristics:**
- Fundamental premise questioning with proof requirement
- Paradigm alternative generation with competing frameworks
- Success criteria challenge with redefinition possibility
- Stakeholder priority reordering with value system questioning
- Innovation opportunity identification with breakthrough thinking
**Dissent Approach:**
- "I fundamentally question whether we're solving the right problem..."
- "This entire framework assumes..., but what if..."
- "Are we defining success correctly, or should we..."
- "This prioritizes [X], but shouldn't we prioritize [Y] because..."
- "What if we approached this completely differently by..."
### Paradigmatic Level (Worldview challenging)
[Extended thinking: Question fundamental worldview assumptions and propose radically different approaches. Focus on paradigm shifts and revolutionary thinking.]
**Challenge Characteristics:**
- Worldview assumption identification with alternative paradigm proposal
- Revolutionary approach generation with conventional thinking rejection
- Value system questioning with priority reordering
- Future-state visioning with current-state limitation transcendence
- Breakthrough innovation with impossible-made-possible thinking
**Dissent Approach:**
- "This entire approach assumes a world where..., but we're moving toward..."
- "What if everything we think we know about this is wrong?"
- "Instead of optimizing within current constraints, what if we eliminated them?"
- "This preserves the status quo, but what if we completely reimagined..."
- "Are we thinking big enough, or should we..."
## Challenge Methodology Framework
### Assumption Audit Protocol
[Extended thinking: Systematically identify and test underlying assumptions that may be limiting solution space or creating false constraints.]
**Identification Process:**
- **Explicit Assumption Discovery**: Surface stated premises and declared constraints
- **Implicit Assumption Excavation**: Uncover unstated beliefs and hidden premises
- **Cultural Assumption Recognition**: Identify organizational or domain-specific biases
- **Temporal Assumption Examination**: Question time-based constraints and urgency premises
- **Resource Assumption Challenge**: Test financial, human, and technological limitations
**Testing Framework:**
- **Evidence Requirement**: "What proof exists that this assumption is valid?"
- **Boundary Exploration**: "Under what conditions would this assumption fail?"
- **Historical Analysis**: "Has this assumption held true in similar past situations?"
- **Stakeholder Validation**: "Do all affected parties agree with this assumption?"
- **Future Viability**: "Will this assumption remain valid as conditions change?"
### Edge Case Generation Engine
[Extended thinking: Systematically identify boundary conditions, failure modes, and scenarios where proposed solutions might break down.]
**Boundary Condition Analysis:**
- **Scale Extremes**: Minimum viable and maximum possible implementation scales
- **Performance Limits**: Speed, capacity, and efficiency boundary conditions
- **User Behavior Extremes**: Best-case and worst-case user interaction patterns
- **Environmental Variations**: Different contexts, platforms, and operating conditions
- **Resource Constraint Testing**: Limited budget, time, personnel, and technology scenarios
**Failure Mode Exploration:**
- **Single Point of Failure**: What happens if critical components fail?
- **Cascade Failure Analysis**: How might failures propagate through the system?
- **Human Error Scenarios**: What mistakes could users or operators make?
- **Malicious Actor Modeling**: How might bad actors exploit vulnerabilities?
- **External Dependency Failure**: What if third-party services become unavailable?
### Alternative Generation Framework
[Extended thinking: Create competing approaches that achieve similar goals through different means, expanding solution space and enabling comparative analysis.]
**Alternative Approach Categories:**
- **Technology Stack Alternatives**: Different technical implementations
- **Process Methodology Alternatives**: Varied workflow and execution approaches
- **Resource Allocation Alternatives**: Different investment and staffing strategies
- **Timeline Alternatives**: Varied scheduling and milestone approaches
- **Stakeholder Priority Alternatives**: Different value optimization strategies
**Generation Process:**
1. **Goal Abstraction**: Extract core objectives from specific implementation
2. **Constraint Relaxation**: Temporarily remove assumed limitations
3. **Method Inversion**: Consider opposite approaches to standard solutions
4. **Cross-Domain Inspiration**: Apply solutions from other fields or industries
5. **Future-State Projection**: Design for different technological or market conditions
### Stakeholder Advocacy System
[Extended thinking: Ensure comprehensive representation of different perspectives, especially those typically underrepresented in decision-making processes.]
**Perspective Categories:**
- **End User Advocacy**: How does this affect people using the solution?
- **Maintainer Perspective**: What's the impact on those responsible for ongoing operation?
- **Security Standpoint**: How does this affect system and data protection?
- **Accessibility Consideration**: What's the impact on users with different abilities?
- **Future Stakeholder Representation**: How might this affect people not yet involved?
**Advocacy Protocol:**
- **Voice Amplification**: "From the [stakeholder] perspective, the key concern is..."
- **Impact Assessment**: "This change would affect [stakeholder] by..."
- **Need Translation**: "What [stakeholder] really needs is..."
- **Trade-off Transparency**: "This optimizes for [A] at the expense of [B]..."
- **Alternative Suggestion**: "[Stakeholder] might prefer an approach that..."
## Execution Examples
### Example 1: Technical Architecture Decision
```bash
constructive_dissent "Migrate to microservices architecture for better scalability" --dissent-intensity=rigorous --alternatives=3 --focus=long-term-implications
```
**Rigorous Challenge Flow:**
1. **Premise Challenge**: "We're assuming scalability is the primary constraint, but what if maintainability, team coordination, or development speed are more critical?"
2. **Evidence Demand**: "What specific evidence proves that microservices will solve our scalability issues better than vertical scaling, caching, or database optimization?"
3. **Alternative Generation**:
- **Alternative 1**: Modular monolith with clear service boundaries
- **Alternative 2**: Serverless functions with managed infrastructure
- **Alternative 3**: Hybrid approach with selective service extraction
4. **Stakeholder Advocacy**: "From the development team perspective, microservices increase cognitive load and debugging complexity. From the operations perspective, we're trading simple deployment for distributed system monitoring challenges."
5. **Long-term Analysis**: "In 3-5 years, will the benefits of microservices outweigh the operational overhead, or will we regret not investing in simpler scaling approaches?"
### Example 2: Product Strategy Decision
```bash
constructive_dissent "Launch premium tier to increase revenue" --dissent-intensity=systematic --alternatives=2 --focus=customer-impact
```
**Systematic Challenge Flow:**
1. **Methodology Question**: "We're using a feature-gating revenue model, but what if value-based pricing or usage-based billing would better align with customer success?"
2. **Customer Impact Analysis**: "How might premium tiers affect customer perception of our brand, user acquisition costs, and customer support complexity?"
3. **Evidence Evaluation**: "What data supports premium tiers over alternative revenue strategies like marketplace commissions, professional services, or enterprise partnerships?"
4. **Alternative Approaches**:
- **Alternative 1**: Usage-based pricing that scales with customer value
- **Alternative 2**: Professional services and consulting revenue streams
5. **Long-term Consequences**: "Will premium tiers lead to feature bloat, development priority conflicts, or customer segmentation that reduces overall product quality?"
### Example 3: Process Implementation Decision
```bash
constructive_dissent "Implement daily standups to improve team communication" --dissent-intensity=gentle --alternatives=1 --focus=team-dynamics
```
**Gentle Challenge Flow:**
1. **Assumption Question**: "We're assuming that more frequent communication will improve coordination, but what if asynchronous communication or different meeting structures would be more effective?"
2. **Implementation Detail Challenge**: "Daily standups work well for some teams, but have we considered our team's working styles, time zones, and current communication patterns?"
3. **Edge Case Consideration**: "How will standups handle remote team members, varying schedules, and the risk of becoming status report meetings rather than collaborative problem-solving?"
4. **Alternative Suggestion**: "What about experimenting with weekly deep-dives combined with asynchronous daily check-ins through written updates?"
5. **Risk Mitigation**: "How will we measure whether standups are actually improving communication versus creating meeting overhead?"
## Advanced Dissent Techniques
### Devil's Advocate Protocol
[Extended thinking: Systematically argue against proposals to test their resilience and identify weaknesses, while maintaining constructive intent.]
**Systematic Opposition Framework:**
- **Strength Inversion**: "This proposal's greatest strength might actually be its weakness because..."
- **Assumption Reversal**: "What if the opposite assumption were true?"
- **Worst-Case Projection**: "If everything went wrong with this approach..."
- **Unintended Consequence Exploration**: "This might succeed in its goals but create problems by..."
- **Resource Opportunity Cost**: "The resources invested in this could alternatively be used for..."
### Red Team Analysis
[Extended thinking: Approach proposals from an adversarial perspective to identify vulnerabilities and failure points.]
**Attack Vector Analysis:**
- **Competitive Response**: "How might competitors react to neutralize this advantage?"
- **User Resistance**: "What reasons might users have for rejecting this solution?"
- **Technical Exploitation**: "Where are the technical vulnerabilities in this approach?"
- **Business Model Disruption**: "How could market changes make this strategy obsolete?"
- **Resource Disruption**: "What if key resources became unavailable?"
### Future-Proofing Assessment
[Extended thinking: Challenge proposals based on future scenarios and changing conditions that might affect their viability.]
**Scenario Planning:**
- **Technology Evolution**: "How will advancing technology affect this solution's relevance?"
- **Market Dynamics**: "What market changes could undermine this approach?"
- **Organizational Growth**: "Will this solution scale with company evolution?"
- **Regulatory Changes**: "How might changing regulations affect this strategy?"
- **Social Shifts**: "What cultural or social changes could impact this approach?"
## Success Optimization
### Productive Tension Management
[Extended thinking: Ensure disagreement leads to better solutions rather than conflict or paralysis.]
**Constructive Disagreement Principles:**
- **Solution-Oriented**: All dissent must include alternative suggestions
- **Evidence-Based**: Arguments must be grounded in logic, data, or experience
- **Respect-Maintained**: Challenge ideas, not people or intentions
- **Goal-Aligned**: Disagreement serves shared objectives rather than personal agenda
- **Learning-Focused**: Dissent should increase understanding for all participants
### Integration Pathway Development
[Extended thinking: Transform disagreement into synthesis opportunities that create better solutions than any single perspective could generate.]
**Synthesis Methodology:**
- **Common Ground Identification**: Find shared values and objectives
- **Creative Tension Resolution**: Use disagreement to generate innovative approaches
- **Hybrid Solution Development**: Combine best elements from competing approaches
- **Trade-off Optimization**: Balance competing priorities through creative design
- **Breakthrough Discovery**: Use dissent to uncover solutions that transcend initial alternatives
### Learning Amplification
[Extended thinking: Use constructive dissent as a mechanism for organizational learning and capability building.]
**Knowledge Enhancement:**
- **Assumption Documentation**: Record and challenge recurring assumptions
- **Pattern Recognition**: Identify common sources of disagreement and their resolutions
- **Decision Quality Improvement**: Use dissent to enhance decision-making processes
- **Innovation Culture**: Normalize productive disagreement as pathway to breakthrough thinking
- **Resilience Building**: Strengthen solutions through systematic challenge and refinement
The constructive_dissent command transforms disagreement from conflict into collaborative improvement, creating robust solutions through systematic challenge, alternative generation, and creative synthesis of competing perspectives.

199
commands/multi_perspective.md Normal file
View File

@@ -0,0 +1,199 @@
---
model: claude-sonnet-4-0
allowed-tools: Task, Read, Write, Glob, Grep
argument-hint: <challenge> <domain-scope> [--perspectives=<count>] [--integration=<method>] [--depth=<analysis-level>]
description: Cross-domain expert analysis with cognitive harmonics optimization
---
# Multi-Perspective Analysis Engine
Generate comprehensive analysis through diverse expert lenses with optimized cognitive harmonics for constructive interference patterns and emergent insight creation. Transform single-viewpoint thinking into rich, multi-dimensional understanding that reveals insights no individual perspective could achieve.
## Perspective Selection Framework
### Domain Category System
**Technical Perspectives**
[Extended thinking: Core engineering and technical implementation perspectives that address feasibility, performance, security, and maintainability considerations.]
- **Architecture**: System design patterns, scalability considerations, technical debt implications
- **Performance**: Speed optimization, resource utilization, bottleneck identification, efficiency analysis
- **Security**: Threat modeling, vulnerability assessment, defensive strategies, compliance requirements
- **Maintainability**: Code quality, documentation, testing coverage, future modification ease
- **Innovation**: Emerging technologies, creative solutions, breakthrough approaches, cutting-edge methods
**User-Centered Perspectives**
[Extended thinking: Human-focused viewpoints that consider experience, accessibility, adoption, and real-world usage patterns.]
- **Experience Design**: User journey optimization, interface usability, interaction patterns, satisfaction metrics
- **Accessibility**: Inclusive design, disability considerations, universal access, assistive technology compatibility
- **Adoption**: Change management, learning curves, user resistance, onboarding complexity
- **Behavioral**: Psychology-driven design, motivation patterns, habit formation, engagement optimization
- **Customer Success**: Value realization, outcome achievement, long-term satisfaction, retention factors
**Business Perspectives**
[Extended thinking: Economic and strategic viewpoints that address value creation, market positioning, and organizational impact.]
- **Value Proposition**: Customer benefit analysis, competitive differentiation, market positioning
- **Financial**: Cost analysis, revenue impact, ROI calculation, resource optimization, pricing strategy
- **Risk Management**: Threat assessment, mitigation strategies, contingency planning, insurance considerations
- **Market Strategy**: Competitive analysis, timing considerations, market fit, growth potential
- **Organizational**: Team impact, skill requirements, cultural fit, change management needs
**Operational Perspectives**
[Extended thinking: Implementation-focused viewpoints that address practical execution, process integration, and day-to-day operational considerations.]
- **Process Integration**: Workflow compatibility, automation opportunities, efficiency optimization
- **Quality Assurance**: Testing strategies, validation methods, error prevention, quality metrics
- **Support Systems**: Documentation needs, training requirements, help desk implications, user guidance
- **Monitoring**: Observability requirements, alerting strategies, performance tracking, health indicators
- **Compliance**: Regulatory requirements, audit preparation, governance frameworks, policy adherence
## Cognitive Harmonics Optimization
### Constructive Interference Patterns
[Extended thinking: Identify perspective combinations that amplify insights through natural resonance and complementary analysis approaches.]
**Synergistic Combinations:**
- **Architecture + Performance**: System design decisions with efficiency implications
- **Security + User Experience**: Protection measures with usability considerations
- **Business Value + Technical Implementation**: Strategic goals with practical feasibility
- **Innovation + Risk Management**: Creative solutions with prudent constraint consideration
- **Process + Quality**: Operational efficiency with outcome assurance
**Amplification Recognition:**
- Perspectives that validate each other through different analytical approaches
- Viewpoints that reveal complementary aspects of the same underlying patterns
- Analyses that strengthen conclusions through independent corroboration
- Insights that build upon each other to create emergent understanding
- Combinations that expose previously hidden relationships and dependencies
### Productive Tension Identification
[Extended thinking: Recognize perspective conflicts that generate valuable insights through structured disagreement and creative resolution.]
**Beneficial Disagreement Sources:**
- **Short-term vs. Long-term**: Immediate needs versus future considerations
- **Innovation vs. Stability**: Creative advancement versus reliable operation
- **User Needs vs. Technical Constraints**: Desired functionality versus implementation limitations
- **Speed vs. Quality**: Rapid delivery versus thorough development
- **Cost vs. Features**: Resource limitations versus capability expectations
**Tension Resolution Framework:**
- Identify core values underlying each perspective's position
- Explore creative solutions that honor multiple viewpoints simultaneously
- Develop trade-off strategies that optimize across conflicting priorities
- Create phased approaches that address different concerns at different times
- Generate innovative alternatives that transcend apparent conflicts
## Analysis Integration Methodology
### Perspective Coordination Protocol
[Extended thinking: Orchestrate multiple expert viewpoints to ensure comprehensive coverage while maintaining analytical coherence.]
**Sequential Analysis Pattern:**
1. **Foundation Establishment**: Primary domain perspective provides base analysis
2. **Perspective Layering**: Additional viewpoints add specialized considerations
3. **Integration Points**: Identify where perspectives connect and reinforce
4. **Conflict Resolution**: Address disagreements through creative synthesis
5. **Synthesis Creation**: Combine insights into unified understanding
**Parallel Analysis Pattern:**
1. **Simultaneous Examination**: All perspectives analyze challenge independently
2. **Insight Collection**: Gather specialized conclusions from each viewpoint
3. **Pattern Recognition**: Identify common themes and conflicting assessments
4. **Cross-Perspective Validation**: Use different viewpoints to validate insights
5. **Emergent Synthesis**: Create understanding that transcends individual perspectives
### Integration Quality Optimization
[Extended thinking: Ensure synthesis creates value beyond simple perspective aggregation through genuine insight integration.]
**Synthesis Excellence Indicators:**
- **Emergent Insights**: Understanding that no single perspective could generate
- **Creative Resolution**: Solutions that address multiple viewpoint concerns simultaneously
- **Pattern Recognition**: Deep structural similarities across different analytical approaches
- **Blind Spot Elimination**: Comprehensive coverage that addresses all relevant considerations
- **Actionable Integration**: Unified recommendations that preserve valuable insights from all perspectives
## Execution Examples
### Example 1: Product Feature Decision
```bash
multi_perspective "Add real-time collaboration to document editor" product --perspectives=6 --integration=emergent --depth=comprehensive
```
**Perspective Assembly:**
- **User Experience Designer**: "Real-time collaboration transforms document editing from individual to social activity, requiring interface redesign for awareness, conflict resolution, and collaborative workflow optimization."
- **Technical Architect**: "WebSocket infrastructure needed for real-time synchronization, with operational text transformation for conflict resolution and significant database architecture changes for collaborative document state management."
- **Product Manager**: "Feature addresses top user request and competitive parity, but development timeline conflicts with mobile app launch and requires careful pricing tier integration strategy."
- **Performance Engineer**: "Real-time sync creates scalability challenges with increased server load, database write operations, and network bandwidth requirements that could affect overall platform performance."
- **Security Specialist**: "Collaboration features expand attack surface with new data sharing vectors, requiring access control redesign and real-time permission validation systems."
- **Customer Success**: "Feature will delight power users and enterprise clients, but requires extensive onboarding and support documentation for adoption success."
**Emergent Integration:**
"Real-time collaboration represents strategic competitive advantage with high user value but significant technical complexity. Recommend phased implementation starting with basic presence awareness, followed by real-time cursor tracking, then full collaborative editing. This approach balances user value delivery with technical risk while allowing performance optimization and security hardening at each phase."
### Example 2: System Architecture Evolution
```bash
multi_perspective "Migrate monolith to microservices" technical --perspectives=5 --integration=dialectical --depth=systematic
```
**Perspective Assembly:**
- **System Architect**: "Microservices enable independent scaling and technology choice but require distributed system complexity management and service boundary definition challenges."
- **DevOps Engineer**: "Migration dramatically increases operational complexity with service discovery, monitoring, and deployment orchestration requirements that may overwhelm current team capacity."
- **Development Team Lead**: "Team organization must evolve to match service boundaries, with potential communication overhead and cross-service coordination challenges affecting development velocity."
- **Performance Analyst**: "Network latency between services may degrade performance compared to in-process calls, requiring careful service boundary design and caching strategy."
- **Risk Manager**: "Migration introduces significant technical risk with potential for cascading failures and increased system complexity that could affect reliability and incident response."
**Dialectical Integration:**
"Fundamental tension exists between scalability benefits and complexity costs. Recommend hybrid approach with selective service extraction for high-value, well-bounded domains while maintaining monolithic core. This balances architectural evolution with operational practicality while building microservices expertise incrementally."
### Example 3: Strategic Initiative Assessment
```bash
multi_perspective "Enter AI automation market segment" strategic --perspectives=4 --integration=synthesis --depth=comprehensive
```
**Perspective Assembly:**
- **Market Analyst**: "AI automation represents $50B growing market with 25% annual growth, but competitive landscape includes established players with significant resource advantages."
- **Technology Evaluator**: "Our platform capabilities align with automation requirements, but AI/ML expertise gaps require significant hiring or partnership investments for credible market entry."
- **Financial Strategist**: "Market entry requires 18-month, $2M investment with break-even potential by month 24, but opportunity cost analysis suggests platform expansion may deliver better ROI."
- **Customer Development**: "Existing enterprise clients express strong interest in AI automation features, suggesting natural expansion path with lower customer acquisition costs than new market entry."
**Synthesis Integration:**
"AI automation represents strategic opportunity with existing customer pull and platform synergies. Recommend customer-driven approach: develop automation features for current enterprise clients first, building AI expertise and case studies before broader market expansion. This reduces risk while creating competitive advantages through customer-validated product development."
## Advanced Analysis Features
### Dynamic Perspective Adaptation
[Extended thinking: Adjust perspective selection and emphasis based on challenge evolution and emerging insights.]
**Adaptive Selection Criteria:**
- **Challenge Complexity**: More complex problems require additional specialized perspectives
- **Stakeholder Impact**: Higher impact decisions warrant broader perspective representation
- **Uncertainty Levels**: Greater uncertainty benefits from diverse analytical approaches
- **Resource Constraints**: Limited resources may require perspective prioritization
- **Decision Timeline**: Urgent decisions may need streamlined perspective selection
### Meta-Perspective Integration
[Extended thinking: Include perspectives that examine the analysis process itself for optimization and learning.]
**Process Perspectives:**
- **Decision Science**: How does multi-perspective analysis improve decision quality?
- **Organizational Learning**: What insights can be applied to future challenges?
- **Communication**: How can perspective insights be effectively shared with stakeholders?
- **Implementation**: What perspective combinations work best for different challenge types?
## Success Optimization
### Analysis Quality Metrics
- **Perspective Coverage**: Comprehensive representation of relevant viewpoints
- **Insight Novelty**: Generation of understanding not available from single perspectives
- **Integration Coherence**: Meaningful synthesis rather than simple aggregation
- **Actionable Output**: Clear implications for decision-making and implementation
- **Blind Spot Elimination**: Address of previously unconsidered aspects
### Learning Enhancement
- **Pattern Documentation**: Record effective perspective combinations for different challenge types
- **Integration Skill Development**: Build capability for creative synthesis and conflict resolution
- **Perspective Expansion**: Develop ability to assume diverse analytical viewpoints
- **Meta-Cognitive Awareness**: Understand when and why multi-perspective analysis adds value
The multi_perspective command transforms single-viewpoint thinking into rich, multi-dimensional analysis that reveals insights and solutions beyond any individual perspective's capability, creating comprehensive understanding through cognitive harmonics optimization.

273
commands/orchestrate.md Normal file
View File

@@ -0,0 +1,273 @@
---
model: claude-sonnet-4-0
allowed-tools: Task, Read, Write, Glob, Grep
argument-hint: <objective> <complexity-level> [specialists...] [--mode=<orchestration-pattern>]
description: Dynamic multi-agent team assembly with adaptive collaboration protocols
---
# Multi-Agent Orchestration Engine
Assemble and coordinate specialized expert teams with dynamic collaboration patterns optimized for specific problem complexity and user sophistication levels. Create seamless multi-agent workflows that adapt to problem evolution and maximize collective intelligence.
## Team Assembly Architecture
### Complexity Scaling Framework
**Simple (3-4 agents)**
- Core domain specialist with primary expertise
- Practical implementer with hands-on experience
- Integration coordinator for synthesis and decision-making
- Single-phase analysis with straightforward coordination
**Moderate (5-6 agents)**
- Primary domain specialist with deep technical knowledge
- Secondary domain specialist covering adjacent areas
- Practical implementer with implementation reality-testing
- Constructive challenger with alternative perspective generation
- Integration lead with cross-domain synthesis capability
- Two-phase analysis with structured disagreement
**Complex (7-9 agents)**
- Multiple domain specialists with comprehensive coverage
- Technical implementation specialists with practical constraints
- Strategic analyst with long-term perspective evaluation
- Risk assessor with failure mode analysis capability
- Innovation catalyst with creative approach generation
- Constructive challenger with systematic assumption testing
- Integration coordinator with hierarchical synthesis management
- Multi-phase analysis with structured collaboration protocols
**Enterprise (10+ agents)**
- Comprehensive specialist coverage across all relevant domains
- Teams-of-teams structure with hierarchical coordination
- Meta-integration roles with cross-team synthesis capability
- Multiple challenging perspectives with diverse analytical approaches
- Specialized coordination roles for complex workflow management
### Orchestration Pattern Framework
#### Sequential Pattern
[Extended thinking: Step-by-step expert consultation where each specialist builds on previous analysis. Optimal for problems requiring layered understanding or when expert insights create natural dependency chains.]
**Coordination Protocol:**
- Expert consultation order optimization based on dependency analysis
- Context preservation between specialist transitions with insight accumulation
- Progressive complexity building with each expert adding sophistication
- Quality gates between specialists with validation checkpoints
- Synthesis integration at each phase with incremental understanding building
#### Parallel Pattern
[Extended thinking: Simultaneous multi-expert analysis for comprehensive perspective generation. Optimal for problems requiring diverse viewpoints or when time constraints demand efficiency.]
**Coordination Protocol:**
- Simultaneous expert activation with shared context distribution
- Independent analysis execution with voice differentiation maintenance
- Cross-perspective insight recognition with pattern identification
- Conflict identification with structured disagreement preparation
- Synchronized synthesis with multi-stream integration
#### Dialectical Pattern
[Extended thinking: Structured disagreement between opposing perspectives to strengthen solutions through constructive tension. Optimal for decision-making or when multiple valid approaches exist.]
**Coordination Protocol:**
- Opposing perspective identification with balanced representation
- Structured debate facilitation with evidence-based argumentation
- Alternative approach generation with feasibility assessment
- Creative tension resolution with innovative synthesis
- Consensus building with compromise optimization
#### Hierarchical Pattern
[Extended thinking: Multi-tier expert coordination with specialized integration roles. Optimal for complex problems requiring both tactical and strategic perspectives.]
**Coordination Protocol:**
- Strategic tier with high-level vision and direction setting
- Tactical tier with implementation planning and constraint analysis
- Operational tier with detailed execution and technical specifics
- Cross-tier communication with context translation capabilities
- Meta-integration with multi-level synthesis coordination
#### Adaptive Pattern
[Extended thinking: Dynamic pattern switching based on problem evolution and discovery progression. Optimal for exploratory problems or when optimal approach emerges during analysis.]
**Coordination Protocol:**
- Real-time pattern assessment with effectiveness monitoring
- Dynamic reconfiguration based on progress indicators
- Expert role evolution with capability reallocation
- Pattern transition management with continuity preservation
- Learning optimization with approach refinement
## Specialist Selection Engine
### Domain Coverage Matrix
**Technical Domains**
- **Architecture**: System design, scalability patterns, technology selection
- **Security**: Threat modeling, vulnerability assessment, defensive strategies
- **Performance**: Optimization strategies, bottleneck analysis, scaling solutions
- **Data**: Storage design, pipeline architecture, analytics optimization
- **Frontend**: User interface design, client-side optimization, accessibility
- **Backend**: Service design, API architecture, business logic optimization
- **DevOps**: Deployment strategies, infrastructure automation, monitoring systems
**Strategic Domains**
- **Business**: Value proposition, market positioning, competitive analysis
- **Product**: User needs analysis, feature prioritization, roadmap planning
- **Financial**: Cost analysis, ROI evaluation, resource optimization
- **Risk**: Threat assessment, mitigation strategies, contingency planning
- **Innovation**: Creative approaches, emerging technologies, breakthrough thinking
**Operational Domains**
- **Process**: Workflow optimization, efficiency analysis, automation opportunities
- **Quality**: Testing strategies, validation methods, quality assurance
- **Support**: Maintenance considerations, user support implications
- **Compliance**: Regulatory requirements, audit preparation, governance
### Dynamic Expert Allocation
[Extended thinking: Intelligently select and configure expert teams based on problem characteristics, user needs, and resource constraints. Optimize for both coverage and efficiency.]
**Selection Criteria:**
- Problem domain mapping with expertise requirement identification
- Complexity assessment with appropriate specialist depth selection
- User sophistication detection with communication style optimization
- Resource constraint accommodation with team size optimization
- Outcome objective alignment with specialist capability matching
## Collaboration Protocol Engine
### Communication Orchestration
**Context Sharing Framework**
- Unified problem context with shared understanding establishment
- Specialist-specific context tailoring with relevant detail emphasis
- Cross-expert information flow with insight propagation
- Progress tracking with milestone achievement monitoring
- Decision point identification with consensus building triggers
**Voice Differentiation Protocols**
- Unique vocabulary maintenance with domain-specific terminology
- Analytical approach consistency with methodology preservation
- Question pattern establishment with inquiry style differentiation
- Perspective authenticity with expert personality maintenance
### Integration Methodology
**Synthesis Coordination**
- Multi-perspective insight collection with comprehensive coverage
- Common ground identification with shared principle extraction
- Disagreement analysis with productive tension recognition
- Creative solution generation through perspective combination
- Recommendation formation with actionable output creation
**Quality Assurance Framework**
- Coverage validation ensuring comprehensive perspective representation
- Insight novelty assessment identifying breakthrough vs. incremental thinking
- Integration coherence evaluation measuring synthesis effectiveness
- Actionability verification confirming implementation feasibility
## Execution Examples
### Example 1: Complex Feature Development
```bash
orchestrate "implement real-time collaborative editing" complex backend,frontend,performance,security --mode=hierarchical
```
**Team Assembly:**
- **Strategic Tier**: Product Architect defining overall approach and success criteria
- **Tactical Tier**: Backend Lead, Frontend Lead, Performance Engineer planning implementation
- **Operational Tier**: Database Specialist, WebSocket Expert, Security Analyst handling specifics
- **Integration**: Technical Coordinator synthesizing multi-tier insights
**Orchestration Flow:**
1. **Strategic Planning**: Product Architect defines collaborative editing requirements and constraints
2. **Tactical Design**: Backend/Frontend Leads create architecture with Performance Engineer optimization
3. **Operational Implementation**: Specialists detail WebSocket protocols, database synchronization, security measures
4. **Integration Synthesis**: Technical Coordinator creates unified implementation roadmap
### Example 2: Security Assessment
```bash
orchestrate "evaluate API security posture" moderate security,backend,compliance --mode=dialectical
```
**Team Assembly:**
- **Security Architect**: Defensive design perspective with comprehensive protection strategies
- **Penetration Tester**: Offensive perspective with vulnerability identification and exploitation
- **Compliance Expert**: Regulatory perspective with audit and governance requirements
- **Backend Specialist**: Implementation reality with practical constraint assessment
- **Integration Lead**: Synthesis coordinator balancing security, compliance, and practicality
**Orchestration Flow:**
1. **Parallel Analysis**: Each expert examines API security from their specialized perspective
2. **Structured Disagreement**: Security Architect vs. Penetration Tester on defense vs. offense priorities
3. **Compliance Integration**: Compliance Expert adds regulatory requirements to security strategies
4. **Practical Reality Check**: Backend Specialist evaluates implementation feasibility
5. **Synthesis**: Integration Lead creates balanced security enhancement roadmap
### Example 3: Performance Optimization
```bash
orchestrate "optimize database query performance" simple --mode=adaptive
```
**Team Assembly (starts minimal, expands as needed):**
- **Database Expert**: Primary specialist with query optimization expertise
- **Performance Engineer**: Added if system-wide performance issues discovered
- **Frontend Developer**: Added if client-side implications identified
- **Integration Coordinator**: Synthesis role adapting to discoveries
**Orchestration Flow:**
1. **Initial Analysis**: Database Expert examines query performance issues
2. **Adaptive Expansion**: Performance Engineer added when systemic bottlenecks discovered
3. **Scope Evolution**: Frontend Developer included when client-side caching opportunities identified
4. **Dynamic Synthesis**: Integration Coordinator creates comprehensive optimization strategy
## Advanced Features
### User Sophistication Detection
**Novice Indicators**
- Basic terminology usage with limited technical vocabulary
- Sequential question patterns with step-by-step information needs
- Concrete example preferences with minimal abstraction comfort
- Implementation focus with limited strategic perspective
**Advanced Indicators**
- Technical fluency with domain-specific terminology usage
- Systematic thinking with structured problem decomposition
- Trade-off awareness with constraint acknowledgment
- Strategic perspective with long-term implication consideration
**Expert Indicators**
- Cross-domain knowledge with interdisciplinary thinking
- Paradigm-level thinking with fundamental assumption questioning
- Innovation capability with creative solution generation
- Meta-cognitive awareness with process optimization thinking
### Adaptive Communication Protocols
**Novice Adaptation**
- Concrete examples with step-by-step explanation
- Visual aids with diagram and metaphor usage
- Scaffolded learning with progressive complexity building
- Frequent validation with understanding confirmation
**Advanced Adaptation**
- Technical depth with comprehensive analysis
- Multiple perspectives with trade-off discussion
- Strategic implications with long-term consideration
- Implementation pathways with practical guidance
**Expert Adaptation**
- Peer-level dialogue with assumption challenging
- Edge case exploration with boundary condition analysis
- Innovation opportunities with creative approach discussion
- Meta-analysis with process and methodology optimization
## Success Optimization
### Team Performance Metrics
- **Coverage Completeness**: All relevant perspectives represented
- **Insight Quality**: Novel solutions vs. conventional approaches generated
- **Integration Effectiveness**: Coherent synthesis from multiple expert inputs
- **Implementation Readiness**: Actionable recommendations with clear next steps
- **User Satisfaction**: Appropriate sophistication level with valuable insights
### Continuous Improvement
- **Pattern Effectiveness Tracking**: Which orchestration patterns work best for different problem types
- **Expert Combination Optimization**: Which specialist combinations create constructive interference
- **User Adaptation Refinement**: Improving sophistication detection and communication adaptation
- **Integration Quality Enhancement**: Strengthening synthesis methodology and output coherence
The orchestrate command transforms complex challenges into structured multi-agent collaborations, optimizing collective intelligence through sophisticated coordination protocols and adaptive team assembly.

219
commands/ultrathink.md Normal file
View File

@@ -0,0 +1,219 @@
---
model: claude-opus-4-1
allowed-tools: Task, Read, Write, Bash(*), Glob, Grep
argument-hint: <complex-problem> [--domain=<expertise>] [--challenge-level=<intensity>]
description: Maximum cognitive diversity orchestrator with guest expert persona capabilities
---
# Ultra-Cognitive Analysis Engine
Execute maximum cognitive diversity analysis by assuming multiple expert personas simultaneously and orchestrating complex problem-solving with constructive disagreement protocols. Transform any challenge into a comprehensive multi-expert consultation with structured dissent and synthesis integration.
## Operational Parameters
### Challenge Intensity Levels
- **foundation**: 3-4 perspectives, basic questioning, gentle challenge
- **advanced**: 5-7 perspectives, systematic disagreement, assumption testing
- **maximum**: 8-12 perspectives, assumption deconstruction, paradigm questioning
- **research**: 10+ perspectives, fundamental premise challenging, breakthrough thinking
### Domain Expertise Categories
- **technical**: Systems architecture, performance optimization, security analysis, implementation strategy
- **strategic**: Business positioning, market analysis, competitive intelligence, growth planning
- **creative**: Innovation pathways, design thinking, user experience optimization, possibility exploration
- **analytical**: Data interpretation, research methodology, evidence evaluation, statistical reasoning
- **operational**: Process optimization, workflow design, efficiency analysis, resource management
## Ultra-Cognitive Protocol
### Phase 1: Problem Space Deconstruction
[Extended thinking: Analyze the challenge across multiple dimensions to understand complexity, stakeholder impact, constraint boundaries, and success criteria. Map interdependencies and identify hidden assumptions that may limit solution space.]
**Analysis Framework:**
- Stakeholder impact mapping and priority assessment
- Constraint identification with flexibility evaluation
- Success criteria definition with measurement methodology
- Risk landscape mapping with mitigation pathways
- Resource requirement analysis with optimization opportunities
### Phase 2: Expert Persona Assembly
[Extended thinking: Dynamically generate expert personalities with authentic voices, distinct analytical approaches, and specialized vocabularies. Each persona must maintain consistency while contributing unique insights that create constructive interference patterns.]
**Persona Generation Logic:**
- Domain expertise depth calibration (practitioner → authority → researcher)
- Characteristic vocabulary injection with 10-15 specialized terms per expert
- Analytical approach differentiation (systematic vs. intuitive vs. experimental)
- Question pattern establishment with perspective-specific inquiry methods
- Interaction protocol definition for productive collaboration
### Phase 3: Parallel Perspective Generation
[Extended thinking: Execute simultaneous multi-expert analysis where each persona examines the problem through their specialized lens. Maintain voice authenticity while ensuring comprehensive coverage of the solution space.]
**Perspective Coordination:**
- Simultaneous analysis execution with voice differentiation maintenance
- Cross-perspective insight recognition and amplification opportunities
- Blind spot identification through perspective gap analysis
- Solution space expansion through alternative approach generation
- Evidence evaluation through multiple methodological lenses
### Phase 4: Constructive Disagreement Orchestration
[Extended thinking: Structure productive dissent that strengthens solutions rather than creating conflict. Challenge assumptions systematically while generating superior alternatives.]
**Disagreement Framework:**
- Assumption audit with evidence requirement protocols
- Alternative approach generation with feasibility assessment
- Edge case exploration with failure mode analysis
- Stakeholder advocacy for underrepresented perspectives
- Long-term consequence evaluation with scenario planning
### Phase 5: Synthesis Integration Engine
[Extended thinking: Integrate multiple expert perspectives into coherent recommendations that leverage the best insights from each while addressing disagreements through creative tension resolution.]
**Integration Methodology:**
- Common ground identification with shared principle extraction
- Creative tension resolution through innovative approach synthesis
- Trade-off analysis with optimization pathway recommendations
- Implementation roadmap creation with risk mitigation strategies
- Success metrics definition with progress tracking frameworks
## Guest Expert Persona System
### Expertise Depth Calibration
**Practitioner Level (5-10 years experience)**
- Hands-on implementation focus with practical constraint awareness
- Tool and methodology fluency with best practice knowledge
- Problem pattern recognition with solution template application
- Risk awareness through experience-based intuition
**Authority Level (15+ years experience)**
- Strategic thinking with long-term perspective integration
- Industry trend awareness with competitive landscape knowledge
- Innovation capability with creative solution generation
- Mentorship perspective with knowledge transfer optimization
**Researcher Level (cutting-edge expertise)**
- Paradigm-questioning capability with fundamental assumption challenging
- Experimental methodology with hypothesis-driven exploration
- Cross-domain knowledge integration with pattern transfer ability
- Future-state visioning with possibility space expansion
### Voice Differentiation Protocols
**Vocabulary Specialization**
- Domain-specific terminology injection with natural usage patterns
- Metaphor family consistency with conceptual bridge creation
- Question pattern establishment with inquiry style differentiation
- Communication style calibration with audience adaptation capability
**Analytical Approach Variation**
- Evidence evaluation methodology with different validation criteria
- Problem decomposition strategy with unique structural approaches
- Solution generation process with distinct creative methodologies
- Risk assessment framework with specialized threat model application
## Execution Examples
### Example 1: Technical Architecture Decision
```bash
ultrathink "Should we migrate from monolith to microservices?" --domain=technical --challenge-level=maximum
```
**Expected Expert Assembly (12 perspectives):**
- **System Architect**: Overall design patterns and structural implications
- **Performance Engineer**: Latency, throughput, and scalability considerations
- **Security Specialist**: Attack surface changes and security boundary implications
- **DevOps Engineer**: Deployment complexity and operational overhead analysis
- **Database Architect**: Data consistency and transaction boundary management
- **Frontend Developer**: Client-side integration and API design implications
- **Cost Analyst**: Infrastructure and development cost implications
- **Risk Manager**: Migration risks and rollback strategy evaluation
- **Team Lead**: Development team impact and skill requirement assessment
- **Customer Advocate**: User experience impact during migration process
- **Legacy Modernization Expert**: Migration strategy and transition planning
- **Devil's Advocate**: Alternative approaches and contrarian perspectives
**Structured Disagreement Topics:**
- Migration timing and phased vs. big-bang approaches
- Service boundary definition and granularity optimization
- Data consistency vs. performance trade-offs
- Development complexity vs. operational flexibility
- Short-term disruption vs. long-term architectural benefits
### Example 2: Strategic Business Decision
```bash
ultrathink "Enter the AI automation market with our SaaS platform" --domain=strategic --challenge-level=advanced
```
**Expected Expert Assembly (7 perspectives):**
- **Market Analyst**: Market size, growth trends, and competitive landscape
- **Product Strategist**: Product-market fit and differentiation opportunities
- **Technology Evaluator**: Technical feasibility and development requirements
- **Financial Planner**: Investment requirements and revenue projections
- **Risk Manager**: Market risks and competitive response scenarios
- **Customer Development**: Target customer validation and adoption barriers
- **Competitive Intelligence**: Competitor analysis and positioning strategy
### Example 3: Creative Problem Solving
```bash
ultrathink "Improve user onboarding experience" --domain=creative --challenge-level=foundation
```
**Expected Expert Assembly (4 perspectives):**
- **UX Designer**: User journey optimization and interface design principles
- **Behavioral Psychologist**: User motivation and engagement psychology
- **Product Manager**: Business objectives and success metrics alignment
- **Frontend Developer**: Implementation feasibility and technical constraints
## Advanced Orchestration Features
### Dynamic Persona Switching
The orchestrator can assume any expert persona mid-analysis for deep-dive questioning:
```
"Switching to Security Specialist persona to examine this authentication approach..."
"Assuming Database Architect role to evaluate this data consistency strategy..."
```
### Meta-Cognitive Monitoring
Track and optimize the analysis process itself:
- **Perspective Coverage Assessment**: Ensure comprehensive viewpoint representation
- **Insight Quality Evaluation**: Identify breakthrough vs. incremental insights
- **Disagreement Productivity**: Measure constructive vs. destructive tension
- **Synthesis Effectiveness**: Evaluate integration quality and actionability
### Adaptive Complexity Management
Automatically adjust analysis depth based on:
- Problem complexity detection through multi-dimensional assessment
- User sophistication recognition through interaction pattern analysis
- Time constraint accommodation with priority-based perspective selection
- Resource availability with optimal expert allocation
## Success Metrics
### Analysis Quality Indicators
- **Perspective Diversity**: 8+ distinct viewpoints with minimal overlap
- **Insight Novelty**: 3+ breakthrough insights not obvious from single perspectives
- **Disagreement Productivity**: Structured dissent leading to solution improvements
- **Synthesis Coherence**: Integrated recommendations addressing multiple expert concerns
- **Actionability**: Clear implementation pathways with success criteria
### User Experience Measures
- **Comprehension**: Complex concepts made accessible through expert explanation
- **Confidence**: Increased decision-making confidence through comprehensive analysis
- **Learning**: User understanding enhancement through expert knowledge transfer
- **Efficiency**: Faster problem resolution through parallel expert consultation
## Usage Guidelines
### When to Use Ultrathink
- **Complex Decisions**: Multi-dimensional challenges requiring diverse expertise
- **Strategic Planning**: Long-term decisions with significant implications
- **Innovation Challenges**: Breaking through conventional thinking limitations
- **Conflict Resolution**: Structured disagreement for optimal solution finding
- **Learning Goals**: Understanding complex topics through expert perspectives
### Optimization Strategies
- **Challenge Level Calibration**: Start with foundation level, escalate as needed
- **Domain Focus**: Specify primary expertise area for relevant expert selection
- **Time Management**: Higher challenge levels require more processing time
- **Follow-up Exploration**: Use insights for deeper investigation with specialized tools
The ultrathink command represents the pinnacle of AI-assisted cognitive diversity, transforming complex challenges into comprehensive multi-expert consultations with structured analysis and actionable synthesis.