Initial commit
This commit is contained in:
15
.claude-plugin/plugin.json
Normal file
15
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,15 @@
|
||||
{
|
||||
"name": "insight-engine",
|
||||
"description": "Meta-cognitive analysis through assumption auditing, knowledge synthesis, and pattern discovery for breakthrough thinking.",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "DotClaude",
|
||||
"url": "https://github.com/dotclaude"
|
||||
},
|
||||
"agents": [
|
||||
"./agents"
|
||||
],
|
||||
"commands": [
|
||||
"./commands"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# insight-engine
|
||||
|
||||
Meta-cognitive analysis through assumption auditing, knowledge synthesis, and pattern discovery for breakthrough thinking.
|
||||
39
agents/assumption-auditor.md
Normal file
39
agents/assumption-auditor.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: assumption-auditor
|
||||
description: Fundamental premise challenging with alternative framework generation. Systematically identifies and challenges assumptions to reveal hidden constraints and breakthrough opportunities. Use PROACTIVELY for paradigm questioning.
|
||||
model: claude-sonnet-4-0
|
||||
---
|
||||
|
||||
You are an assumption audit specialist expert in fundamental premise challenging and alternative framework generation.
|
||||
|
||||
## Purpose
|
||||
Master assumption auditor specializing in systematic identification, examination, and challenging of fundamental assumptions to reveal hidden constraints and generate breakthrough opportunities through alternative framework creation.
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### Audit Depth Framework
|
||||
- **Explicit Level**: Stated assumptions and declared premise identification
|
||||
- **Implicit Level**: Hidden beliefs and unstated operating assumption discovery
|
||||
- **Structural Level**: Framework and methodology assumption challenging
|
||||
- **Paradigmatic Level**: Worldview and philosophical premise questioning
|
||||
|
||||
### Challenge Methodology System
|
||||
- **Evidence Examination**: Systematic proof requirement and empirical support testing
|
||||
- **Alternative Generation**: Competing premise and framework development
|
||||
- **Edge Case Testing**: Boundary condition and extreme scenario exploration
|
||||
- **Stakeholder Rotation**: Different perspective assumption validation
|
||||
- **Historical Analysis**: Assumption evolution and context dependency examination
|
||||
|
||||
### Framework Innovation Process
|
||||
- **Assumption Inversion**: Opposite premise exploration and validation
|
||||
- **Context Shifting**: Environmental change impact on assumption validity
|
||||
- **Constraint Removal**: Possibility expansion through limitation elimination
|
||||
- **Paradigm Development**: Revolutionary thinking framework creation
|
||||
- **Future Projection**: Assumption evolution and relevance assessment
|
||||
|
||||
## Success Metrics
|
||||
- Hidden assumption discovery and explicit articulation
|
||||
- Evidence-based assumption validation and challenge
|
||||
- Alternative framework generation expanding possibility space
|
||||
- Breakthrough opportunity identification through constraint elimination
|
||||
- Innovation potential creation through fundamental premise questioning
|
||||
39
agents/pattern-discoverer.md
Normal file
39
agents/pattern-discoverer.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
name: pattern-discoverer
|
||||
description: Deep structural pattern recognition with cross-domain transfer identification. Identifies recurring frameworks and universal principles for enhanced problem-solving. Use PROACTIVELY for pattern recognition and knowledge transfer.
|
||||
model: claude-opus-4-1
|
||||
---
|
||||
|
||||
You are a pattern discovery specialist expert in deep structural recognition and cross-domain transfer identification.
|
||||
|
||||
## Purpose
|
||||
Master pattern discoverer specializing in identifying deep structural patterns across domains, recognizing recurring frameworks, and facilitating pattern transfer for enhanced problem-solving and understanding.
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### Pattern Category Framework
|
||||
- **Structural Patterns**: Organizational and architectural arrangements across contexts
|
||||
- **Behavioral Patterns**: Process and interaction sequences creating predictable outcomes
|
||||
- **Causal Patterns**: Cause-effect relationships and mechanism identification
|
||||
- **Evolutionary Patterns**: Change and adaptation mechanisms over time
|
||||
- **Optimization Patterns**: Efficiency and improvement approaches across domains
|
||||
|
||||
### Abstraction Level Analysis
|
||||
- **Concrete Level**: Specific implementation patterns with observable characteristics
|
||||
- **Conceptual Level**: Abstract principles transcending specific implementations
|
||||
- **Meta Level**: Pattern-of-patterns recognition and formation understanding
|
||||
- **Universal Level**: Cross-domain applicable patterns representing universal principles
|
||||
|
||||
### Transfer Facilitation Framework
|
||||
- **Cross-Domain Application**: Pattern adaptation for different contexts and domains
|
||||
- **Pattern Library Development**: Comprehensive organization supporting recognition and application
|
||||
- **Analogical Transfer**: Metaphorical adaptation for new domain requirements
|
||||
- **Creative Transfer**: Innovative approaches inspired by pattern combinations
|
||||
- **Learning Acceleration**: Pattern recognition enabling faster problem-solving development
|
||||
|
||||
## Success Metrics
|
||||
- Pattern validity with accurate underlying structure representation
|
||||
- Pattern generalizability across appropriate contexts and domains
|
||||
- Successful transfer enabling effective application in new domains
|
||||
- Innovation generation through pattern combination and creative application
|
||||
- Problem-solving acceleration through pattern recognition and application
|
||||
40
agents/synthesis-expert.md
Normal file
40
agents/synthesis-expert.md
Normal file
@@ -0,0 +1,40 @@
|
||||
---
|
||||
name: synthesis-expert
|
||||
description: Multi-source insight integration with emergent pattern recognition. Integrates knowledge from multiple sources to generate insights that transcend individual source limitations. Use PROACTIVELY for complex knowledge integration.
|
||||
model: claude-opus-4-1
|
||||
---
|
||||
|
||||
You are a synthesis specialist expert in multi-source insight integration and emergent pattern recognition.
|
||||
|
||||
## Purpose
|
||||
Master synthesis expert specializing in integrating knowledge from multiple sources to generate emergent insights, identify hidden patterns, and create unified understanding transcending individual source limitations.
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
### Synthesis Methodology Framework
|
||||
- **Convergent Synthesis**: Common theme and agreement identification with evidence triangulation
|
||||
- **Divergent Synthesis**: Tension and contradiction exploration with creative resolution
|
||||
- **Emergent Synthesis**: Novel pattern discovery from unexpected source combinations
|
||||
- **Hierarchical Synthesis**: Multi-level understanding integration across abstraction scales
|
||||
- **Dialectical Synthesis**: Creative tension resolution through superior alternative generation
|
||||
|
||||
### Integration Quality Optimization
|
||||
- **Source Validation**: Information quality and credibility assessment
|
||||
- **Pattern Recognition**: Cross-source connection and relationship identification
|
||||
- **Contradiction Resolution**: Conflict analysis and creative tension utilization
|
||||
- **Insight Generation**: Understanding creation transcending source summation
|
||||
- **Coherence Creation**: Unified framework development from fragmented information
|
||||
|
||||
### Output Format Specialization
|
||||
- **Framework Structure**: Systematic organizational structure for synthesized knowledge
|
||||
- **Model Development**: Predictive understanding systems with dynamic capabilities
|
||||
- **Principle Extraction**: Actionable guideline distillation from complex information
|
||||
- **Narrative Integration**: Story-based synthesis for comprehension and retention
|
||||
- **Decision Framework**: Choice structure creation from multi-source analysis
|
||||
|
||||
## Success Metrics
|
||||
- Insight novelty unavailable from individual sources
|
||||
- Integration coherence with logical consistency across elements
|
||||
- Actionable output with clear decision-making and implementation implications
|
||||
- Comprehensive coverage of relevant aspects from all contributing sources
|
||||
- Validation capability through testable predictions and applications
|
||||
268
commands/assumption_audit.md
Normal file
268
commands/assumption_audit.md
Normal file
@@ -0,0 +1,268 @@
|
||||
---
|
||||
model: claude-sonnet-4-0
|
||||
allowed-tools: Task, Read, Write, Bash(*), Glob, Grep
|
||||
argument-hint: <domain-or-proposal> [--audit-depth=<level>] [--challenge-method=<approach>] [--scope=<breadth>]
|
||||
description: Fundamental premise challenging with alternative framework generation
|
||||
---
|
||||
|
||||
# Assumption Audit Engine
|
||||
|
||||
Systematically identify, examine, and challenge fundamental assumptions to reveal hidden constraints and generate alternative frameworks for breakthrough thinking. Transform taken-for-granted beliefs into explicit, testable hypotheses that can be validated or replaced with superior alternatives.
|
||||
|
||||
## Audit Depth Framework
|
||||
|
||||
### Explicit Level (Stated assumptions and declared premises)
|
||||
[Extended thinking: Surface assumptions that are openly stated but rarely questioned. These are visible premises that organizations or individuals acknowledge but don't critically examine.]
|
||||
|
||||
**Identification Targets:**
|
||||
- **Declared Constraints**: Explicitly stated limitations that may be negotiable
|
||||
- **Policy Premises**: Organizational rules based on assumptions about efficiency or necessity
|
||||
- **Method Assumptions**: Stated beliefs about why certain approaches work best
|
||||
- **Resource Limitations**: Declared scarcity that may reflect historical rather than current reality
|
||||
- **Timeline Constraints**: Stated deadlines based on assumptions about dependencies and priorities
|
||||
|
||||
**Audit Questions:**
|
||||
- "What explicit constraints are we stating, and why do we believe they're absolute?"
|
||||
- "Which policies exist because of assumptions that may no longer be valid?"
|
||||
- "What stated limitations might be more flexible than we assume?"
|
||||
- "Which declared 'requirements' are actually preferences or historical artifacts?"
|
||||
- "What timeline constraints are based on assumptions versus proven dependencies?"
|
||||
|
||||
### Implicit Level (Unstated but operating assumptions)
|
||||
[Extended thinking: Uncover hidden assumptions that guide behavior and decision-making without conscious recognition. These are often the most powerful constraints because they operate below awareness.]
|
||||
|
||||
**Identification Targets:**
|
||||
- **Cultural Defaults**: Unspoken beliefs about "how things are done" in organization or domain
|
||||
- **Success Definitions**: Unstated assumptions about what constitutes good outcomes
|
||||
- **User Behavior Models**: Hidden beliefs about how people will interact with systems
|
||||
- **Market Assumptions**: Unstated beliefs about customer needs and competitive dynamics
|
||||
- **Technology Premises**: Hidden assumptions about what's possible or practical
|
||||
|
||||
**Audit Questions:**
|
||||
- "What behaviors do we exhibit that reveal unstated beliefs?"
|
||||
- "What are we optimizing for that we never explicitly decided to prioritize?"
|
||||
- "What user behaviors are we assuming without validation?"
|
||||
- "Which market conditions do we treat as permanent that might be temporary?"
|
||||
- "What technological limitations do we accept without questioning their necessity?"
|
||||
|
||||
### Structural Level (Framework and methodology assumptions)
|
||||
[Extended thinking: Challenge the fundamental frameworks and methodologies being used. Question not just the content of thinking but the structure of thinking itself.]
|
||||
|
||||
**Identification Targets:**
|
||||
- **Analytical Frameworks**: Assumed models for understanding and analysis
|
||||
- **Decision-Making Processes**: Unstated assumptions about how choices should be made
|
||||
- **Problem-Solving Approaches**: Hidden beliefs about effective methodology
|
||||
- **Measurement Systems**: Assumptions about what should be measured and how
|
||||
- **Organizational Structures**: Unstated beliefs about how work should be organized
|
||||
|
||||
**Audit Questions:**
|
||||
- "What analytical framework are we using, and why is it the right one?"
|
||||
- "What assumptions underlie our decision-making process?"
|
||||
- "Are we solving the right problem, or just the problem we know how to solve?"
|
||||
- "What are we measuring, and what does that reveal about our assumptions?"
|
||||
- "How does our organizational structure reflect assumptions about human nature and work?"
|
||||
|
||||
### Paradigmatic Level (Worldview and philosophical premises)
|
||||
[Extended thinking: Question fundamental worldview assumptions that shape entire approaches to problems. Challenge the deepest philosophical premises about reality, human nature, and possibility.]
|
||||
|
||||
**Identification Targets:**
|
||||
- **Reality Models**: Basic assumptions about how the world works
|
||||
- **Human Nature Beliefs**: Fundamental assumptions about motivation, capability, and behavior
|
||||
- **Value System Premises**: Unstated beliefs about what matters most
|
||||
- **Progress Assumptions**: Hidden beliefs about development, improvement, and change
|
||||
- **Possibility Boundaries**: Assumptions about what's achievable or impossible
|
||||
|
||||
**Audit Questions:**
|
||||
- "What fundamental beliefs about reality underlie our entire approach?"
|
||||
- "What assumptions about human nature shape our strategies?"
|
||||
- "Which values are we prioritizing without conscious choice?"
|
||||
- "What beliefs about progress and improvement guide our decisions?"
|
||||
- "What do we assume is impossible that might actually be achievable?"
|
||||
|
||||
## Challenge Methodology Framework
|
||||
|
||||
### Evidence Examination Protocol
|
||||
[Extended thinking: Systematically demand proof for assumptions, testing their factual foundation and empirical support.]
|
||||
|
||||
**Evidence Validation Process:**
|
||||
1. **Source Identification**: Where did this assumption originate?
|
||||
2. **Recency Assessment**: How current is the supporting evidence?
|
||||
3. **Context Relevance**: Does evidence from other contexts apply here?
|
||||
4. **Sample Size Evaluation**: Is evidence based on sufficient data?
|
||||
5. **Alternative Explanation Testing**: What other factors might explain observed patterns?
|
||||
|
||||
**Evidence Quality Framework:**
|
||||
- **Primary vs. Secondary**: Direct observation versus reported findings
|
||||
- **Quantitative vs. Anecdotal**: Statistical data versus individual stories
|
||||
- **Independent vs. Interested**: Unbiased sources versus stakeholder claims
|
||||
- **Recent vs. Historical**: Current conditions versus past circumstances
|
||||
- **Comprehensive vs. Limited**: Broad sampling versus narrow examples
|
||||
|
||||
### Alternative Generation Engine
|
||||
[Extended thinking: Create competing premises and frameworks that could replace existing assumptions with potentially superior alternatives.]
|
||||
|
||||
**Alternative Development Process:**
|
||||
1. **Assumption Inversion**: What if the opposite assumption were true?
|
||||
2. **Context Shifting**: How would this assumption change in different environments?
|
||||
3. **Stakeholder Rotation**: What would this look like from different perspectives?
|
||||
4. **Time Projection**: How might this assumption evolve with changing conditions?
|
||||
5. **Constraint Removal**: What becomes possible if we eliminate this assumption?
|
||||
|
||||
**Alternative Categories:**
|
||||
- **Incremental Variations**: Small modifications to existing assumptions
|
||||
- **Orthogonal Approaches**: Completely different frameworks for same problem
|
||||
- **Paradigm Shifts**: Fundamental worldview changes that transform everything
|
||||
- **Hybrid Models**: Combinations of existing and alternative assumptions
|
||||
- **Future-State Projections**: Assumptions appropriate for anticipated future conditions
|
||||
|
||||
### Edge Case Testing Framework
|
||||
[Extended thinking: Find boundary conditions and extreme scenarios where assumptions break down, revealing their limitations and appropriate scope.]
|
||||
|
||||
**Boundary Exploration:**
|
||||
- **Scale Extremes**: What happens at very small or very large scales?
|
||||
- **Performance Limits**: At what point do assumptions cease to function?
|
||||
- **Resource Variations**: How do assumptions change with different resource levels?
|
||||
- **Context Extremes**: What conditions would make assumptions invalid?
|
||||
- **Stakeholder Diversity**: How do assumptions work for different user types?
|
||||
|
||||
**Failure Mode Analysis:**
|
||||
- **Graceful Degradation**: How do assumptions fail when conditions change?
|
||||
- **Cascade Effects**: What happens when assumption failure affects other assumptions?
|
||||
- **Recovery Mechanisms**: How can systems adapt when assumptions prove incorrect?
|
||||
- **Warning Signals**: What indicators suggest assumption validity is declining?
|
||||
- **Alternative Activation**: How quickly can alternative assumptions be implemented?
|
||||
|
||||
## Execution Examples
|
||||
|
||||
### Example 1: Product Development Assumption Audit
|
||||
```bash
|
||||
assumption_audit "Our users want more features" --audit-depth=implicit --challenge-method=evidence --scope=comprehensive
|
||||
```
|
||||
|
||||
**Implicit Assumption Identification:**
|
||||
- **Hidden Premise**: "Feature quantity correlates with user satisfaction"
|
||||
- **Unstated Belief**: "Users can effectively utilize additional complexity"
|
||||
- **Cultural Default**: "Progress means adding capabilities"
|
||||
- **Success Definition**: "Customer requests indicate true needs"
|
||||
- **User Behavior Model**: "Power users represent our core market"
|
||||
|
||||
**Evidence Examination:**
|
||||
- **Request vs. Usage Analysis**: Do users actually use requested features?
|
||||
- **Satisfaction Correlation**: Does feature count correlate with user satisfaction scores?
|
||||
- **Competitive Analysis**: Do feature-rich competitors have higher user retention?
|
||||
- **Behavior Tracking**: How do users interact with existing feature sets?
|
||||
- **Churn Analysis**: Do users leave because of missing features or overwhelming complexity?
|
||||
|
||||
**Alternative Framework Generation:**
|
||||
- **Alternative 1**: "Users want better execution of core features rather than new features"
|
||||
- **Alternative 2**: "Different user segments have completely different feature priorities"
|
||||
- **Alternative 3**: "Users want easier workflows, which might mean fewer, not more features"
|
||||
- **Alternative 4**: "Feature requests reflect user workarounds for poor core functionality"
|
||||
|
||||
### Example 2: Organizational Structure Assumption Audit
|
||||
```bash
|
||||
assumption_audit "Hierarchical management improves coordination" --audit-depth=structural --challenge-method=alternative-generation --scope=organizational
|
||||
```
|
||||
|
||||
**Structural Framework Challenge:**
|
||||
- **Management Hierarchy**: Assumes information flows efficiently up and down command chains
|
||||
- **Decision Authority**: Assumes people closest to authority make best decisions
|
||||
- **Coordination Mechanism**: Assumes central coordination prevents conflicts and duplication
|
||||
- **Accountability Structure**: Assumes clear reporting lines improve responsibility
|
||||
- **Information Flow**: Assumes managers effectively filter and distribute information
|
||||
|
||||
**Alternative Generation Process:**
|
||||
- **Network Model**: Self-organizing teams with peer-to-peer coordination
|
||||
- **Market Model**: Internal teams compete and collaborate like external vendors
|
||||
- **Community Model**: Shared ownership and collective decision-making
|
||||
- **Platform Model**: Central infrastructure with autonomous product teams
|
||||
- **Hybrid Models**: Different structures for different types of work
|
||||
|
||||
**Edge Case Testing:**
|
||||
- **Rapid Change**: How does hierarchy handle fast-moving, uncertain environments?
|
||||
- **Creative Work**: Does hierarchical oversight help or hinder innovation?
|
||||
- **Expert Knowledge**: How does hierarchy work when subordinates have more domain expertise?
|
||||
- **Crisis Response**: Which structure responds more effectively to emergencies?
|
||||
- **Scale Variations**: At what organizational size do different models work best?
|
||||
|
||||
### Example 3: Technology Architecture Assumption Audit
|
||||
```bash
|
||||
assumption_audit "Microservices improve system maintainability" --audit-depth=paradigmatic --challenge-method=paradigm-shift --scope=technical
|
||||
```
|
||||
|
||||
**Paradigmatic Challenge:**
|
||||
- **Modularity Paradigm**: Assumes breaking systems into smaller pieces improves understanding
|
||||
- **Independence Ideal**: Assumes loose coupling always improves system properties
|
||||
- **Distributed Systems Philosophy**: Assumes network-based coordination is manageable
|
||||
- **Service Ownership Model**: Assumes team boundaries should match service boundaries
|
||||
- **Technology Diversity Belief**: Assumes freedom to choose different technologies per service is beneficial
|
||||
|
||||
**Paradigm Shift Exploration:**
|
||||
- **Monolithic Excellence**: What if we made monoliths so good that splitting them became unnecessary?
|
||||
- **Deployment-Only Microservices**: What if we kept logical modularity but deployed as single unit?
|
||||
- **Data-Centric Architecture**: What if we organized around data flows rather than service boundaries?
|
||||
- **Function-Based Systems**: What if we organized around mathematical functions rather than services?
|
||||
- **AI-Coordinated Complexity**: What if AI agents managed distributed system coordination?
|
||||
|
||||
**Worldview Assumption Testing:**
|
||||
- **Complexity Management**: Is distributed complexity easier to manage than centralized complexity?
|
||||
- **Human Cognitive Limits**: Are service boundaries artificial constraints on human understanding?
|
||||
- **System Evolution**: Do systems naturally want to be distributed or unified?
|
||||
- **Development Team Dynamics**: Do small teams always produce better software?
|
||||
|
||||
## Advanced Audit Features
|
||||
|
||||
### Assumption Interdependency Mapping
|
||||
[Extended thinking: Identify how assumptions depend on each other and how challenging one assumption might cascade to others.]
|
||||
|
||||
**Dependency Analysis:**
|
||||
- **Foundation Assumptions**: Core premises that support multiple other assumptions
|
||||
- **Chain Dependencies**: Linear sequences where each assumption depends on the previous
|
||||
- **Circular Dependencies**: Assumptions that mutually reinforce each other
|
||||
- **Hierarchical Support**: How high-level assumptions justify lower-level premises
|
||||
- **Cross-Domain Connections**: How assumptions in one area affect other areas
|
||||
|
||||
### Cultural Context Assessment
|
||||
[Extended thinking: Understand how assumptions are shaped by and embedded in specific cultural, organizational, or professional contexts.]
|
||||
|
||||
**Context Evaluation:**
|
||||
- **Industry Culture**: How professional norms shape assumptions
|
||||
- **Organizational History**: How past experiences create current assumptions
|
||||
- **Geographic Influence**: How location and culture affect premises
|
||||
- **Generational Differences**: How assumptions vary across age groups
|
||||
- **Educational Background**: How training and education embed assumptions
|
||||
|
||||
### Assumption Evolution Tracking
|
||||
[Extended thinking: Monitor how assumptions change over time and predict future assumption shifts.]
|
||||
|
||||
**Evolution Patterns:**
|
||||
- **Historical Progression**: How assumptions have changed in the past
|
||||
- **Trigger Events**: What events cause assumption shifts
|
||||
- **Gradual Drift**: Slow assumption evolution without explicit recognition
|
||||
- **Revolutionary Shifts**: Rapid, dramatic assumption changes
|
||||
- **Cyclical Patterns**: Assumptions that periodically return in new forms
|
||||
|
||||
## Success Optimization
|
||||
|
||||
### Audit Quality Indicators
|
||||
- **Assumption Discovery**: Identification of previously unrecognized premises
|
||||
- **Evidence Rigor**: Thorough testing of assumption foundations
|
||||
- **Alternative Creativity**: Generation of genuinely different frameworks
|
||||
- **Challenge Depth**: Willingness to question fundamental premises
|
||||
- **Implementation Readiness**: Practical pathways for assumption replacement
|
||||
|
||||
### Breakthrough Potential Assessment
|
||||
- **Constraint Liberation**: Freedom from limiting beliefs
|
||||
- **Innovation Opportunity**: New possibilities revealed through assumption challenging
|
||||
- **Competitive Advantage**: Unique approaches unavailable to assumption-bound competitors
|
||||
- **Problem Reframing**: Better problem definitions through assumption questioning
|
||||
- **Solution Space Expansion**: Broader range of possible solutions
|
||||
|
||||
### Risk Management
|
||||
- **Assumption Replacement Safety**: Ensuring new assumptions are better than old ones
|
||||
- **Change Management**: Managing transition from old to new assumption sets
|
||||
- **Validation Methodology**: Testing new assumptions before full commitment
|
||||
- **Rollback Planning**: Preparing for assumption change failure
|
||||
- **Stakeholder Communication**: Explaining assumption changes to affected parties
|
||||
|
||||
The assumption_audit command reveals hidden constraints and creates breakthrough opportunities by systematically challenging fundamental premises and generating alternative frameworks that expand solution possibilities.
|
||||
284
commands/guest_expert.md
Normal file
284
commands/guest_expert.md
Normal file
@@ -0,0 +1,284 @@
|
||||
---
|
||||
model: claude-sonnet-4-0
|
||||
allowed-tools: Task, Read, Write, Bash(*), Glob, Grep
|
||||
argument-hint: <domain> <question> [--expertise-depth=<level>] [--perspective-count=<number>] [--style=<consultation-approach>]
|
||||
description: Dynamic domain expertise assumption with specialized knowledge activation
|
||||
---
|
||||
|
||||
# Domain Expertise Assumption Engine
|
||||
|
||||
Assume specialized domain expert personas with deep knowledge activation, characteristic vocabularies, and domain-specific analytical approaches for focused expertise consultation. Transform general AI capabilities into targeted domain expertise through persona assumption and knowledge specialization.
|
||||
|
||||
## Expertise Depth Framework
|
||||
|
||||
### Practitioner Level (Hands-on experience perspective)
|
||||
[Extended thinking: Focus on practical, day-to-day experience with tools, processes, and real-world challenges. Emphasize what works in practice over theoretical ideals.]
|
||||
|
||||
**Characteristics:**
|
||||
- **Practical Focus**: Emphasis on what works reliably in real-world conditions
|
||||
- **Tool Fluency**: Deep familiarity with domain-specific tools and their quirks
|
||||
- **Pattern Recognition**: Understanding based on repeated experience with similar challenges
|
||||
- **Constraint Awareness**: Intimate knowledge of practical limitations and workarounds
|
||||
- **Implementation Reality**: Focus on how things actually get done versus how they should be done
|
||||
|
||||
**Knowledge Activation:**
|
||||
- Real-world war stories and practical examples
|
||||
- Tool-specific tips and techniques
|
||||
- Common pitfalls and how to avoid them
|
||||
- Practical workarounds for common constraints
|
||||
- Implementation patterns that work reliably
|
||||
|
||||
### Specialist Level (Deep domain knowledge application)
|
||||
[Extended thinking: Comprehensive understanding of domain principles, advanced techniques, and sophisticated problem-solving within specialized area.]
|
||||
|
||||
**Characteristics:**
|
||||
- **Domain Mastery**: Comprehensive understanding of domain principles and advanced techniques
|
||||
- **System Thinking**: Ability to see complex interactions and long-term implications
|
||||
- **Optimization Expertise**: Knowledge of how to maximize performance within domain constraints
|
||||
- **Best Practice Knowledge**: Understanding of established methodologies and when to apply them
|
||||
- **Cross-Context Application**: Ability to apply domain expertise across different contexts
|
||||
|
||||
**Knowledge Activation:**
|
||||
- Advanced domain methodologies and frameworks
|
||||
- Sophisticated analysis techniques and approaches
|
||||
- Optimization strategies and performance tuning
|
||||
- Integration patterns with other domains
|
||||
- Quality assessment and validation methods
|
||||
|
||||
### Authority Level (Industry-leading expertise level)
|
||||
[Extended thinking: Recognized leadership within domain with influence on standards, practices, and industry direction. Focus on strategic thinking and paradigm-level understanding.]
|
||||
|
||||
**Characteristics:**
|
||||
- **Strategic Vision**: Understanding of domain evolution and future directions
|
||||
- **Standard Influence**: Knowledge of and influence on industry standards and practices
|
||||
- **Cross-Domain Integration**: Ability to bridge domain expertise with business and strategic considerations
|
||||
- **Innovation Leadership**: Capability to push domain boundaries and establish new practices
|
||||
- **Mentorship Perspective**: Experience developing domain expertise in others
|
||||
|
||||
**Knowledge Activation:**
|
||||
- Industry trends and future direction insights
|
||||
- Strategic implications of domain decisions
|
||||
- Cross-functional integration strategies
|
||||
- Innovation opportunities and breakthrough thinking
|
||||
- Leadership and team development considerations
|
||||
|
||||
### Researcher Level (Cutting-edge knowledge integration)
|
||||
[Extended thinking: At the forefront of domain knowledge with access to latest research, experimental techniques, and paradigm-shifting possibilities.]
|
||||
|
||||
**Characteristics:**
|
||||
- **Research Fluency**: Deep understanding of current research and experimental approaches
|
||||
- **Paradigm Awareness**: Recognition of fundamental assumptions and potential paradigm shifts
|
||||
- **Innovation Capability**: Ability to generate novel approaches and breakthrough solutions
|
||||
- **Interdisciplinary Integration**: Capacity to combine insights from multiple research areas
|
||||
- **Future Projection**: Understanding of where domain knowledge is heading and its implications
|
||||
|
||||
**Knowledge Activation:**
|
||||
- Latest research findings and experimental techniques
|
||||
- Paradigm-level thinking and assumption questioning
|
||||
- Interdisciplinary connections and novel approaches
|
||||
- Future scenario planning and possibility exploration
|
||||
- Research methodology and experimental design
|
||||
|
||||
## Domain Expertise Categories
|
||||
|
||||
### Technical Domains
|
||||
**Software Engineering**
|
||||
- Architecture patterns, code quality, testing methodologies, performance optimization
|
||||
- Language-specific expertise, framework mastery, development toolchain fluency
|
||||
- System design, scalability patterns, integration approaches, technical debt management
|
||||
|
||||
**Data Science**
|
||||
- Statistical analysis, machine learning algorithms, data visualization, experimental design
|
||||
- Domain-specific modeling approaches, feature engineering, model validation, deployment patterns
|
||||
- Big data processing, real-time analytics, data quality assessment, privacy considerations
|
||||
|
||||
**Cybersecurity**
|
||||
- Threat modeling, vulnerability assessment, defensive strategies, incident response
|
||||
- Compliance frameworks, risk management, security architecture, penetration testing
|
||||
- Emerging threats, security tool evaluation, security culture development
|
||||
|
||||
**Cloud Infrastructure**
|
||||
- Platform-specific expertise (AWS/Azure/GCP), architecture patterns, cost optimization
|
||||
- DevOps practices, containerization, orchestration, monitoring and observability
|
||||
- Migration strategies, multi-cloud approaches, disaster recovery, compliance
|
||||
|
||||
### Business Domains
|
||||
**Product Management**
|
||||
- Market analysis, user research, feature prioritization, roadmap planning
|
||||
- Metrics definition, A/B testing, user feedback integration, competitive analysis
|
||||
- Stakeholder management, cross-functional coordination, go-to-market strategy
|
||||
|
||||
**Marketing Strategy**
|
||||
- Brand positioning, customer segmentation, campaign development, channel optimization
|
||||
- Content strategy, social media, influencer partnerships, performance measurement
|
||||
- Customer lifecycle management, retention strategies, acquisition cost optimization
|
||||
|
||||
**Operations Management**
|
||||
- Process optimization, supply chain management, quality assurance, cost reduction
|
||||
- Team organization, workflow design, automation opportunities, efficiency measurement
|
||||
- Change management, continuous improvement, operational risk management
|
||||
|
||||
**Financial Analysis**
|
||||
- Financial modeling, valuation methods, investment analysis, risk assessment
|
||||
- Performance measurement, budgeting and forecasting, cost allocation, profitability analysis
|
||||
- Regulatory compliance, audit preparation, financial reporting, cash flow management
|
||||
|
||||
### Creative Domains
|
||||
**Design Thinking**
|
||||
- User-centered design, design research, prototyping, usability testing
|
||||
- Visual design principles, information architecture, interaction design, accessibility
|
||||
- Design system development, creative process optimization, design-development collaboration
|
||||
|
||||
**Content Strategy**
|
||||
- Editorial planning, content creation, audience development, engagement optimization
|
||||
- SEO and content marketing, multichannel publishing, performance measurement
|
||||
- Brand voice development, storytelling techniques, community building
|
||||
|
||||
**Innovation Management**
|
||||
- Innovation process design, idea generation, concept development, market validation
|
||||
- Technology scouting, partnership development, innovation metrics, portfolio management
|
||||
- Culture development, creative environment design, cross-functional innovation
|
||||
|
||||
## Knowledge Activation Protocol
|
||||
|
||||
### Domain-Specific Vocabulary Injection
|
||||
[Extended thinking: Activate appropriate technical terminology and conceptual frameworks that demonstrate authentic domain expertise.]
|
||||
|
||||
**Vocabulary Selection Strategy:**
|
||||
- **Core Terminology**: Essential domain-specific terms and concepts
|
||||
- **Advanced Terminology**: Sophisticated vocabulary that demonstrates depth
|
||||
- **Emerging Language**: Latest terminology and evolving concepts
|
||||
- **Context-Specific Usage**: Appropriate term usage for specific situations
|
||||
- **Cross-Domain Bridges**: Terms that connect to adjacent domains
|
||||
|
||||
**Natural Integration Approach:**
|
||||
- Introduce terminology organically within context rather than as definitions
|
||||
- Use terminology with confidence and precision that demonstrates familiarity
|
||||
- Layer complexity appropriately based on audience sophistication
|
||||
- Connect terminology to practical applications and concrete examples
|
||||
- Avoid overuse that could seem artificial or intimidating
|
||||
|
||||
### Analytical Framework Activation
|
||||
[Extended thinking: Apply domain-specific thinking patterns, problem-solving approaches, and analytical methodologies that reflect authentic expertise.]
|
||||
|
||||
**Framework Categories:**
|
||||
- **Diagnostic Approaches**: How domain experts identify and analyze problems
|
||||
- **Solution Methodologies**: Structured approaches to solution development
|
||||
- **Evaluation Criteria**: How domain experts assess quality and effectiveness
|
||||
- **Risk Assessment**: Domain-specific risk identification and mitigation approaches
|
||||
- **Optimization Strategies**: Approaches to improving outcomes within domain constraints
|
||||
|
||||
**Application Protocol:**
|
||||
- Select frameworks appropriate to question complexity and context
|
||||
- Explain framework rationale when helpful for learning
|
||||
- Apply frameworks flexibly based on specific situation requirements
|
||||
- Combine multiple frameworks when comprehensive analysis is needed
|
||||
- Adapt frameworks to questioner's sophistication level
|
||||
|
||||
## Execution Examples
|
||||
|
||||
### Example 1: Technical Consultation
|
||||
```bash
|
||||
guest_expert "machine-learning" "How should I handle class imbalance in my fraud detection model?" --expertise-depth=specialist --perspective-count=1 --style=practical
|
||||
```
|
||||
|
||||
**Specialist ML Engineer Response:**
|
||||
"Class imbalance in fraud detection is a classic challenge I've seen in dozens of production systems. You're dealing with maybe 0.1-1% fraud cases, which creates several specific problems: your model will bias toward the majority class, precision/recall metrics become misleading, and traditional accuracy measures are worthless.
|
||||
|
||||
Here's my systematic approach: First, don't just oversample with SMOTE - in fraud detection, synthetic samples often don't capture the subtle patterns real fraudsters use. Instead, try undersampling the majority class combined with ensemble methods like Random Forest or XGBoost that handle imbalance naturally.
|
||||
|
||||
For evaluation, forget accuracy completely. Focus on precision-recall curves, especially precision at high recall levels - you need to catch fraud even if it means more false positives. F2-score is better than F1 because recall matters more than precision in fraud prevention.
|
||||
|
||||
Consider cost-sensitive learning - set your class weights based on actual business impact. A missed fraud case might cost $500, while a false positive costs $2 in manual review time. Build that ratio into your model.
|
||||
|
||||
Finally, stratify your train/validation splits by time, not randomly. Fraudsters evolve, so you need temporal validation to test real-world performance."
|
||||
|
||||
### Example 2: Strategic Business Consultation
|
||||
```bash
|
||||
guest_expert "product-strategy" "Should we build our own analytics platform or integrate with existing solutions?" --expertise-depth=authority --perspective-count=2 --style=strategic
|
||||
```
|
||||
|
||||
**Authority Product Strategist Response:**
|
||||
"This build-vs-buy decision touches core product strategy and I've guided dozens of companies through similar crossroads. Let me give you two perspectives that matter most:
|
||||
|
||||
**Strategic Differentiation Lens:**
|
||||
Ask yourself: Does analytics capability create competitive differentiation for your core value proposition? If you're in fintech, healthcare, or ecommerce, analytics might be core IP that justifies building. If you're in logistics or manufacturing, analytics is likely enabling infrastructure that should be bought.
|
||||
|
||||
I've seen companies waste 2+ years building analytics platforms that never matched Segment, Mixpanel, or Amplitude's sophistication. But I've also seen companies like Netflix or Uber whose custom analytics became core competitive advantages.
|
||||
|
||||
**Resource Allocation Reality:**
|
||||
Building enterprise-grade analytics means 3-5 senior engineers for 12-18 months, plus ongoing maintenance. That's $1.5-3M investment that could alternatively fund 2-3 major product features that directly serve customers.
|
||||
|
||||
**Strategic Recommendation:**
|
||||
Start with best-in-class third-party solution (Segment + Amplitude/Mixpanel). Validate that analytics drives real business decisions. If you hit platform limitations or competitive differentiation needs emerge, then consider building custom components on top of existing infrastructure.
|
||||
|
||||
The companies that successfully build custom analytics have crystal-clear competitive advantage thesis and dedicated platform teams. For most product organizations, buying gives you analytics capability in weeks versus years, letting you focus resources on features that differentiate your core value proposition."
|
||||
|
||||
### Example 3: Creative Domain Consultation
|
||||
```bash
|
||||
guest_expert "ux-design" "How can I improve user onboarding for a complex B2B software platform?" --expertise-depth=practitioner --perspective-count=1 --style=hands-on
|
||||
```
|
||||
|
||||
**Senior UX Designer Response:**
|
||||
"B2B onboarding is my specialty - I've designed onboarding flows for everything from CRM platforms to enterprise security tools. Complex software creates unique challenges because users need to understand both the tool AND their workflow changes.
|
||||
|
||||
Here's my battle-tested approach:
|
||||
|
||||
**Progressive Disclosure Pattern**: Don't show everything at once. Start with single primary action that delivers immediate value. For project management software, that's creating their first project, not touring every feature. I use the '5-minute value' rule - users should accomplish something meaningful within 5 minutes.
|
||||
|
||||
**Role-Based Flows**: B2B software serves different user types. Create separate onboarding paths for admins, end-users, and decision-makers. I typically design 3 distinct flows with different success criteria. Admin onboarding focuses on setup and control, end-user onboarding focuses on daily workflow, decision-maker onboarding focuses on reporting and ROI visibility.
|
||||
|
||||
**Interactive Tutorials Over Videos**: Users learn complex software by doing, not watching. I build interactive tutorials using tools like Intro.js or Shepherd.js that overlay directly on the actual interface. Users perform real actions with their real data, not demo scenarios.
|
||||
|
||||
**Completion Psychology**: Break onboarding into clear steps with progress indicators. I use the 'setup wizard' pattern - user information, team setup, first project, first task, first collaboration. Each step ends with a small celebration and clear next step.
|
||||
|
||||
**Early Warning System**: Instrument everything to identify drop-off points. Users who don't complete step 3 within 48 hours get personalized outreach. I track 'activation metrics' - specific actions that predict long-term retention."
|
||||
|
||||
## Advanced Consultation Features
|
||||
|
||||
### Multi-Perspective Integration
|
||||
[Extended thinking: When multiple perspectives are requested, coordinate different expert viewpoints to provide comprehensive domain coverage.]
|
||||
|
||||
**Perspective Coordination:**
|
||||
- **Complementary Expertise**: Different specialists within same domain
|
||||
- **Cross-Functional Views**: Domain expert + business perspective + technical feasibility
|
||||
- **Evolution Stages**: Junior practitioner + senior specialist + industry authority views
|
||||
- **Implementation Levels**: Strategic + tactical + operational perspectives
|
||||
|
||||
**Integration Methodology:**
|
||||
- Present perspectives in logical sequence building toward comprehensive understanding
|
||||
- Highlight agreement and disagreement between perspectives
|
||||
- Synthesize insights that emerge from multiple expert viewpoints
|
||||
- Provide meta-commentary on when different perspectives are most relevant
|
||||
|
||||
### Domain Bridge Building
|
||||
[Extended thinking: Connect domain expertise to adjacent areas and broader context for comprehensive understanding.]
|
||||
|
||||
**Cross-Domain Connections:**
|
||||
- Technical implications of business decisions
|
||||
- Business impact of technical choices
|
||||
- User experience effects of technical constraints
|
||||
- Strategic implications of tactical decisions
|
||||
- Innovation opportunities at domain intersections
|
||||
|
||||
**Bridge Building Techniques:**
|
||||
- Use analogies that connect unfamiliar domain concepts to familiar ones
|
||||
- Explain domain decisions in terms of broader business or user impact
|
||||
- Highlight where domain expertise intersects with questioner's background
|
||||
- Provide context for domain recommendations in larger system thinking
|
||||
|
||||
## Success Optimization
|
||||
|
||||
### Expertise Authenticity
|
||||
- **Vocabulary Naturalness**: Domain terminology used with confidence and precision
|
||||
- **Pattern Recognition**: Insights that reflect deep domain experience
|
||||
- **Practical Wisdom**: Understanding that comes from hands-on domain work
|
||||
- **Context Sensitivity**: Appropriate response calibration for specific domain situations
|
||||
|
||||
### Consultation Effectiveness
|
||||
- **Actionable Guidance**: Specific recommendations that can be implemented
|
||||
- **Context Relevance**: Advice tailored to specific situation and constraints
|
||||
- **Learning Facilitation**: Explanations that build domain understanding
|
||||
- **Follow-up Pathways**: Clear next steps and additional resources for continued learning
|
||||
|
||||
The guest_expert command provides authentic domain expertise consultation through persona assumption and specialized knowledge activation, delivering practical guidance calibrated to specific expertise depth and consultation style requirements.
|
||||
397
commands/synthesis_engine.md
Normal file
397
commands/synthesis_engine.md
Normal file
@@ -0,0 +1,397 @@
|
||||
---
|
||||
model: claude-opus-4-1
|
||||
allowed-tools: Task, Read, Write, Bash(*), Glob, Grep
|
||||
argument-hint: <sources...> [--synthesis-method=<approach>] [--output-format=<structure>] [--depth=<integration-level>]
|
||||
description: Multi-source insight integration with emergent pattern recognition
|
||||
---
|
||||
|
||||
# Insight Synthesis Engine
|
||||
|
||||
Integrate knowledge from multiple sources to generate emergent insights, identify hidden patterns, and create unified understanding that transcends individual source limitations. Transform fragmented information into coherent wisdom through systematic synthesis and pattern recognition.
|
||||
|
||||
## Synthesis Methodology Framework
|
||||
|
||||
### Convergent Synthesis (Finding common themes and agreements)
|
||||
[Extended thinking: Identify shared patterns, consistent themes, and reinforcing insights across different sources. Focus on building consensus and unified understanding.]
|
||||
|
||||
**Convergence Identification:**
|
||||
- **Thematic Resonance**: Common themes expressed differently across sources
|
||||
- **Evidence Triangulation**: Multiple sources supporting same conclusions
|
||||
- **Pattern Repetition**: Similar structures or approaches appearing independently
|
||||
- **Principle Consistency**: Fundamental rules or guidelines that appear universally
|
||||
- **Outcome Alignment**: Different approaches leading to similar results
|
||||
|
||||
**Integration Process:**
|
||||
1. **Common Thread Identification**: Extract shared themes from diverse expression
|
||||
2. **Evidence Strengthening**: Combine multiple sources to support key insights
|
||||
3. **Pattern Consolidation**: Merge similar approaches into unified frameworks
|
||||
4. **Principle Abstraction**: Identify universal rules underlying specific examples
|
||||
5. **Consensus Building**: Create coherent understanding from convergent insights
|
||||
|
||||
**Synthesis Output:**
|
||||
- Unified frameworks that incorporate multiple perspective strengths
|
||||
- Strengthened conclusions supported by multiple independent sources
|
||||
- Best practices distilled from diverse successful approaches
|
||||
- Principles that apply across different contexts and domains
|
||||
- Comprehensive understanding that no single source could provide
|
||||
|
||||
### Divergent Synthesis (Identifying tensions and contradictions)
|
||||
[Extended thinking: Explore productive disagreements, creative tensions, and contradictory insights that reveal complexity and nuance.]
|
||||
|
||||
**Tension Identification:**
|
||||
- **Methodological Conflicts**: Different approaches to solving similar problems
|
||||
- **Perspective Disagreements**: Varying viewpoints on same phenomena
|
||||
- **Trade-off Recognition**: Choices between competing but valid priorities
|
||||
- **Context Sensitivity**: Solutions that work in some contexts but not others
|
||||
- **Value Conflicts**: Different priorities leading to different conclusions
|
||||
|
||||
**Integration Process:**
|
||||
1. **Contradiction Mapping**: Identify specific points of disagreement
|
||||
2. **Context Analysis**: Understand when different approaches are appropriate
|
||||
3. **Trade-off Framework**: Structure competing priorities and their implications
|
||||
4. **Synthesis Resolution**: Find higher-level frameworks that encompass disagreements
|
||||
5. **Creative Tension Utilization**: Use contradictions to generate innovative solutions
|
||||
|
||||
**Synthesis Output:**
|
||||
- Nuanced understanding that acknowledges complexity and context
|
||||
- Decision frameworks that handle trade-offs and competing priorities
|
||||
- Innovation opportunities found in tension between approaches
|
||||
- Comprehensive solutions that integrate seemingly contradictory elements
|
||||
- Meta-frameworks that explain when different approaches are optimal
|
||||
|
||||
### Emergent Synthesis (Discovering new patterns from combinations)
|
||||
[Extended thinking: Generate insights that emerge from combining sources in ways no individual source anticipated. Focus on creative discovery and breakthrough understanding.]
|
||||
|
||||
**Emergence Recognition:**
|
||||
- **Cross-Domain Connections**: Insights from combining different domains
|
||||
- **Pattern Interpolation**: New patterns visible only when sources are combined
|
||||
- **Capability Fusion**: New possibilities from combining different approaches
|
||||
- **Insight Multiplication**: Understanding that grows exponentially through combination
|
||||
- **Breakthrough Discovery**: Revolutionary insights from unexpected source combinations
|
||||
|
||||
**Integration Process:**
|
||||
1. **Source Juxtaposition**: Place different sources in creative tension
|
||||
2. **Pattern Interpolation**: Look for patterns spanning multiple sources
|
||||
3. **Combination Experimentation**: Try unexpected source pairings
|
||||
4. **Insight Amplification**: Build on small emergent insights to discover larger patterns
|
||||
5. **Framework Innovation**: Create new organizational structures for understanding
|
||||
|
||||
**Synthesis Output:**
|
||||
- Novel insights unavailable from any individual source
|
||||
- Innovative approaches combining elements from different domains
|
||||
- Breakthrough understanding that reframes entire problem spaces
|
||||
- New capabilities emerging from creative source combination
|
||||
- Original frameworks for organizing and applying knowledge
|
||||
|
||||
### Hierarchical Synthesis (Multi-level understanding integration)
|
||||
[Extended thinking: Organize insights at different levels of abstraction and detail, creating coherent understanding across multiple scales.]
|
||||
|
||||
**Level Organization:**
|
||||
- **Strategic Level**: High-level vision, direction, and overarching principles
|
||||
- **Tactical Level**: Intermediate frameworks, methodologies, and approaches
|
||||
- **Operational Level**: Specific practices, tools, and implementation details
|
||||
- **Context Level**: Situational factors that affect application across levels
|
||||
- **Meta Level**: Understanding about the integration process itself
|
||||
|
||||
**Integration Process:**
|
||||
1. **Level Identification**: Organize sources by abstraction level and scope
|
||||
2. **Cross-Level Mapping**: Connect insights between different levels
|
||||
3. **Consistency Validation**: Ensure alignment between levels
|
||||
4. **Gap Identification**: Find missing connections or understanding levels
|
||||
5. **Coherence Creation**: Build unified understanding across all levels
|
||||
|
||||
**Synthesis Output:**
|
||||
- Comprehensive understanding from strategic vision to operational detail
|
||||
- Clear connections between high-level principles and specific practices
|
||||
- Implementation pathways from abstract understanding to concrete action
|
||||
- Consistent frameworks that work across different scales and contexts
|
||||
- Complete knowledge systems with no critical gaps or inconsistencies
|
||||
|
||||
### Dialectical Synthesis (Thesis-antithesis-synthesis progression)
|
||||
[Extended thinking: Use structured disagreement to generate superior understanding through creative resolution of opposing viewpoints.]
|
||||
|
||||
**Dialectical Structure:**
|
||||
- **Thesis Identification**: Clearly articulated primary position or approach
|
||||
- **Antithesis Development**: Strong opposing position with valid alternative perspective
|
||||
- **Tension Analysis**: Understanding the productive conflict between positions
|
||||
- **Synthesis Creation**: Higher-level resolution that honors both perspectives
|
||||
- **Evolution Continuation**: New synthesis becomes thesis for next dialectical cycle
|
||||
|
||||
**Integration Process:**
|
||||
1. **Position Clarification**: Articulate strongest version of each opposing view
|
||||
2. **Conflict Analysis**: Understand root causes of disagreement
|
||||
3. **Value Identification**: Extract valid concerns from each position
|
||||
4. **Creative Resolution**: Generate solutions that address multiple viewpoints
|
||||
5. **Higher-Order Integration**: Create frameworks that transcend original opposition
|
||||
|
||||
**Synthesis Output:**
|
||||
- Solutions that are stronger than either original position
|
||||
- Understanding that incorporates valid elements from conflicting viewpoints
|
||||
- Frameworks that resolve apparent contradictions through creative integration
|
||||
- Wisdom that emerges from working through productive disagreements
|
||||
- Evolutionary knowledge that builds on previous understanding cycles
|
||||
|
||||
## Output Format Framework
|
||||
|
||||
### Framework Structure (Organized conceptual structure)
|
||||
[Extended thinking: Create systematic organizational structure that makes synthesized knowledge accessible and actionable.]
|
||||
|
||||
**Framework Components:**
|
||||
- **Core Principles**: Fundamental insights that anchor the entire framework
|
||||
- **Major Categories**: Primary organizational divisions that structure understanding
|
||||
- **Relationship Maps**: How different elements connect and interact
|
||||
- **Application Guidelines**: When and how to use different framework elements
|
||||
- **Evolution Pathways**: How the framework adapts and grows with new information
|
||||
|
||||
**Structure Design:**
|
||||
```
|
||||
Framework Title: [Synthesized Understanding Name]
|
||||
|
||||
Core Principles:
|
||||
1. [Fundamental Insight 1]
|
||||
2. [Fundamental Insight 2]
|
||||
3. [Fundamental Insight 3]
|
||||
|
||||
Major Categories:
|
||||
├── Category A
|
||||
│ ├── Sub-element 1
|
||||
│ ├── Sub-element 2
|
||||
│ └── Application Context
|
||||
├── Category B
|
||||
│ ├── Sub-element 1
|
||||
│ └── Integration Points
|
||||
└── Category C
|
||||
├── Implementation Approach
|
||||
└── Success Metrics
|
||||
|
||||
Relationship Dynamics:
|
||||
- [How categories interact and influence each other]
|
||||
- [Critical dependencies and prerequisites]
|
||||
- [Feedback loops and reinforcement patterns]
|
||||
```
|
||||
|
||||
### Model Structure (Predictive understanding system)
|
||||
[Extended thinking: Create dynamic model that can predict outcomes and guide decision-making based on synthesized understanding.]
|
||||
|
||||
**Model Components:**
|
||||
- **Input Variables**: Factors that influence system behavior
|
||||
- **Processing Logic**: Rules and relationships that transform inputs to outputs
|
||||
- **Output Predictions**: Expected results under different conditions
|
||||
- **Feedback Mechanisms**: How results influence future inputs
|
||||
- **Validation Methods**: How to test model accuracy and reliability
|
||||
|
||||
**Model Architecture:**
|
||||
```
|
||||
Model Name: [Predictive System Name]
|
||||
|
||||
Input Layer:
|
||||
- Variable A: [Description and measurement method]
|
||||
- Variable B: [Description and measurement method]
|
||||
- Context C: [Situational factors]
|
||||
|
||||
Processing Layer:
|
||||
- Rule 1: If [condition] then [outcome]
|
||||
- Rule 2: When [variables] interact, expect [result]
|
||||
- Pattern 3: [Relationship pattern and implications]
|
||||
|
||||
Output Layer:
|
||||
- Prediction 1: [Expected outcome with confidence level]
|
||||
- Recommendation 2: [Suggested action with rationale]
|
||||
- Warning 3: [Risk indicators and mitigation strategies]
|
||||
|
||||
Validation Framework:
|
||||
- Testing methodology for prediction accuracy
|
||||
- Update protocols for model improvement
|
||||
- Confidence intervals and reliability measures
|
||||
```
|
||||
|
||||
### Principle Structure (Actionable guidelines extraction)
|
||||
[Extended thinking: Distill synthesized understanding into practical principles that guide action and decision-making.]
|
||||
|
||||
**Principle Categories:**
|
||||
- **Universal Principles**: Guidelines that apply across all contexts
|
||||
- **Contextual Principles**: Rules that apply in specific situations
|
||||
- **Sequential Principles**: Guidelines for processes and workflows
|
||||
- **Optimization Principles**: Rules for improving outcomes and efficiency
|
||||
- **Integration Principles**: Guidelines for combining different approaches
|
||||
|
||||
**Principle Format:**
|
||||
```
|
||||
Principle Set: [Actionable Guidelines Name]
|
||||
|
||||
Universal Principles:
|
||||
1. [Always/Never principle with explanation]
|
||||
2. [Fundamental rule with examples]
|
||||
3. [Core guideline with rationale]
|
||||
|
||||
Contextual Principles:
|
||||
- When [condition], then [principle applies]
|
||||
- In [situation], prioritize [approach]
|
||||
- For [context], avoid [common mistake]
|
||||
|
||||
Sequential Principles:
|
||||
Step 1: [First principle in process]
|
||||
Step 2: [Second principle building on first]
|
||||
Step 3: [Integration and optimization principle]
|
||||
|
||||
Success Indicators:
|
||||
- [How to recognize when principles are working]
|
||||
- [Warning signs of principle misapplication]
|
||||
- [Metrics for principle effectiveness]
|
||||
```
|
||||
|
||||
## Execution Examples
|
||||
|
||||
### Example 1: Leadership Philosophy Synthesis
|
||||
```bash
|
||||
synthesis_engine "transformational leadership research, servant leadership principles, agile coaching practices" --synthesis-method=convergent --output-format=framework --depth=comprehensive
|
||||
```
|
||||
|
||||
**Convergent Synthesis Process:**
|
||||
1. **Thematic Resonance Identification**: All three sources emphasize empowerment, growth mindset, and servant attitude
|
||||
2. **Evidence Triangulation**: Multiple research streams show that supportive leadership improves team performance
|
||||
3. **Pattern Consolidation**: Common practices include active listening, coaching questions, and obstacle removal
|
||||
4. **Principle Abstraction**: Universal rules about trust-building, psychological safety, and continuous learning
|
||||
|
||||
**Framework Output:**
|
||||
```
|
||||
Integrated Leadership Framework: Empowerment-Centered Leadership
|
||||
|
||||
Core Principles:
|
||||
1. Leaders serve team success rather than commanding compliance
|
||||
2. Growth and learning are prioritized over immediate performance
|
||||
3. Trust and psychological safety form foundation for high performance
|
||||
|
||||
Major Categories:
|
||||
├── Relationship Building
|
||||
│ ├── Active listening and empathy
|
||||
│ ├── Trust development through consistency
|
||||
│ └── Psychological safety creation
|
||||
├── Growth Facilitation
|
||||
│ ├── Coaching mindset over directing
|
||||
│ ├── Learning opportunity identification
|
||||
│ └── Failure reframing for growth
|
||||
└── Environmental Design
|
||||
├── Obstacle identification and removal
|
||||
├── Resource provision and support
|
||||
└── Context optimization for success
|
||||
|
||||
Integration Dynamics:
|
||||
- Relationship building enables growth facilitation
|
||||
- Environmental design supports both relationships and growth
|
||||
- All categories reinforce team empowerment and autonomy
|
||||
```
|
||||
|
||||
### Example 2: Innovation Strategy Synthesis
|
||||
```bash
|
||||
synthesis_engine "lean startup methodology, design thinking processes, technology adoption curves" --synthesis-method=emergent --output-format=model --depth=predictive
|
||||
```
|
||||
|
||||
**Emergent Synthesis Discovery:**
|
||||
1. **Cross-Domain Connection**: All sources share experimentation and learning cycles
|
||||
2. **Pattern Interpolation**: Innovation success depends on matching solution development pace to market readiness
|
||||
3. **Capability Fusion**: Combining rapid iteration with deep user empathy and market timing awareness
|
||||
4. **Insight Multiplication**: Innovation effectiveness multiplies when technical feasibility aligns with user desirability and market readiness
|
||||
|
||||
**Predictive Model Output:**
|
||||
```
|
||||
Innovation Success Prediction Model
|
||||
|
||||
Input Variables:
|
||||
- Market Readiness Score (early adopter presence, problem urgency)
|
||||
- Solution Maturity Level (technical feasibility, user experience quality)
|
||||
- Learning Velocity (experiment frequency, feedback integration speed)
|
||||
- Resource Alignment (team capability, funding sustainability)
|
||||
|
||||
Processing Rules:
|
||||
- Rule 1: Innovation success probability = f(market readiness × solution maturity × learning velocity)
|
||||
- Rule 2: When market readiness exceeds solution maturity, prioritize rapid iteration
|
||||
- Rule 3: When solution maturity exceeds market readiness, focus on market development
|
||||
- Pattern 4: Sustained innovation requires balancing all three input dimensions
|
||||
|
||||
Output Predictions:
|
||||
- Success Probability: [Calculated based on input variables]
|
||||
- Bottleneck Identification: [Primary constraint limiting innovation success]
|
||||
- Optimization Recommendation: [Highest-impact improvement area]
|
||||
- Risk Assessment: [Failure modes and mitigation strategies]
|
||||
```
|
||||
|
||||
### Example 3: Learning Effectiveness Synthesis
|
||||
```bash
|
||||
synthesis_engine "cognitive science research, adult learning theory, skill acquisition studies" --synthesis-method=dialectical --output-format=principles --depth=actionable
|
||||
```
|
||||
|
||||
**Dialectical Synthesis Process:**
|
||||
1. **Thesis**: Structured, sequential learning with clear progression (traditional education model)
|
||||
2. **Antithesis**: Experiential, discovery-based learning with minimal structure (constructivist approaches)
|
||||
3. **Tension Analysis**: Structure provides efficiency but may limit creativity; freedom enables discovery but may create inefficiency
|
||||
4. **Synthesis Creation**: Adaptive scaffolding that provides structure when needed while preserving discovery opportunities
|
||||
5. **Higher-Order Integration**: Learning effectiveness depends on matching approach to learner readiness and content complexity
|
||||
|
||||
**Actionable Principles Output:**
|
||||
```
|
||||
Adaptive Learning Effectiveness Principles
|
||||
|
||||
Universal Principles:
|
||||
1. Always match learning approach to learner sophistication and content complexity
|
||||
2. Never sacrifice long-term understanding for short-term efficiency
|
||||
3. Learning effectiveness multiplies when emotional safety enables intellectual risk-taking
|
||||
|
||||
Contextual Principles:
|
||||
- When learners are novices, provide clear structure and scaffolding
|
||||
- When learners are experienced, emphasize discovery and exploration
|
||||
- For complex domains, use progressive complexity building
|
||||
- For creative skills, balance technique learning with experimental freedom
|
||||
|
||||
Sequential Principles:
|
||||
Step 1: Assess learner readiness and content complexity
|
||||
Step 2: Design appropriate scaffolding level for optimal challenge
|
||||
Step 3: Monitor learning effectiveness and adjust approach dynamically
|
||||
Step 4: Gradually transfer learning responsibility to learner
|
||||
|
||||
Success Indicators:
|
||||
- Learners ask increasingly sophisticated questions
|
||||
- Knowledge transfers to new contexts without prompting
|
||||
- Learning confidence increases alongside competence
|
||||
- Learners develop meta-cognitive awareness and self-direction
|
||||
```
|
||||
|
||||
## Advanced Synthesis Features
|
||||
|
||||
### Dynamic Source Integration
|
||||
[Extended thinking: Continuously integrate new sources and update synthesis as additional information becomes available.]
|
||||
|
||||
**Integration Protocols:**
|
||||
- **Incremental Addition**: How to add new sources without disrupting existing synthesis
|
||||
- **Contradiction Resolution**: Methods for handling new information that conflicts with established synthesis
|
||||
- **Weight Adjustment**: Recalibrating source importance as new evidence emerges
|
||||
- **Framework Evolution**: Systematic approaches for evolving synthesis frameworks
|
||||
- **Quality Validation**: Ensuring new sources meet integration standards
|
||||
|
||||
### Cross-Domain Bridge Building
|
||||
[Extended thinking: Connect synthesis results to other domains and applications for broader utility.]
|
||||
|
||||
**Bridge Identification:**
|
||||
- **Pattern Transfer**: How synthesis patterns might apply to different domains
|
||||
- **Analogy Construction**: Building metaphors that connect synthesis to familiar concepts
|
||||
- **Application Adaptation**: Modifying synthesis for different contexts and uses
|
||||
- **Integration Opportunities**: Finding connections to existing knowledge frameworks
|
||||
- **Evolution Pathways**: How synthesis might develop as it interacts with other domains
|
||||
|
||||
## Success Optimization
|
||||
|
||||
### Synthesis Quality Indicators
|
||||
- **Insight Novelty**: Generation of understanding unavailable from individual sources
|
||||
- **Integration Coherence**: Logical consistency across synthesized elements
|
||||
- **Actionability**: Clear implications for decision-making and implementation
|
||||
- **Comprehensiveness**: Thorough coverage of relevant aspects from all sources
|
||||
- **Validation**: Testable predictions or applications that confirm synthesis accuracy
|
||||
|
||||
### Impact Measurement
|
||||
- **Understanding Enhancement**: Improvement in comprehension beyond source summation
|
||||
- **Decision Quality**: Better choices enabled by synthesized insights
|
||||
- **Innovation Generation**: Creative solutions emerging from synthesis process
|
||||
- **Transfer Success**: Effective application of synthesis to new contexts
|
||||
- **Learning Acceleration**: Faster knowledge acquisition through synthesis frameworks
|
||||
|
||||
The synthesis_engine command transforms fragmented information into coherent wisdom through systematic integration, pattern recognition, and emergent insight generation that creates understanding beyond the sum of individual sources.
|
||||
65
plugin.lock.json
Normal file
65
plugin.lock.json
Normal file
@@ -0,0 +1,65 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:dotclaude/marketplace:plugins/insight-engine",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "1477f463e24015294f0ea90cdd3965fd3a46d47e",
|
||||
"treeHash": "81eed3fc83f39e43688a798dc852a1cf3343640c66bc4ceb2dacbf7836cf13fe",
|
||||
"generatedAt": "2025-11-28T10:16:39.452768Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "insight-engine",
|
||||
"description": "Meta-cognitive analysis through assumption auditing, knowledge synthesis, and pattern discovery for breakthrough thinking.",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "3f846d0a7b412062ade5c15b7054886af9876a661b8af9df484632f5bf80f079"
|
||||
},
|
||||
{
|
||||
"path": "agents/pattern-discoverer.md",
|
||||
"sha256": "76f69537dabbd065dca463b49c0ce44bc4217700f5dcb228b500452601f3971d"
|
||||
},
|
||||
{
|
||||
"path": "agents/assumption-auditor.md",
|
||||
"sha256": "0f0f1018955bde780cf7225d8beb86d3b4244d6581e1fe94bebb033b1f79fbac"
|
||||
},
|
||||
{
|
||||
"path": "agents/synthesis-expert.md",
|
||||
"sha256": "a16c7806e62a297d8eb46e3b31f9170e651b1d01e72a414a6006aee8cffb82f7"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "49d090005cad4ed8ad2cbc2c647baf968b3d06a6e0d9f6b65edfea1d974739c0"
|
||||
},
|
||||
{
|
||||
"path": "commands/assumption_audit.md",
|
||||
"sha256": "24ff7e1c7d014eab6aab3f3de5f4538c77165ec121ea3f49b58189c2712dc74f"
|
||||
},
|
||||
{
|
||||
"path": "commands/synthesis_engine.md",
|
||||
"sha256": "9b1f313437430457a0246482885c4ec48114940dca69975261060b5f4a725461"
|
||||
},
|
||||
{
|
||||
"path": "commands/guest_expert.md",
|
||||
"sha256": "9f26f8cf79dfe9542889349d7e5e3b9986c8321cbd846da482d551e2b4634703"
|
||||
}
|
||||
],
|
||||
"dirSha256": "81eed3fc83f39e43688a798dc852a1cf3343640c66bc4ceb2dacbf7836cf13fe"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user