mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-11 02:33:51 +08:00
refactor: Reduce duplication in brainstorming system
- Create brainstorming-framework.md to centralize common techniques and execution modes - Simplify conceptual-planning-agent.md from 280 to 170 lines (39% reduction) - Update all 9 brainstorm commands to reference framework instead of agent - Eliminate circular dependencies and improve maintainability Key improvements: - Separated concerns: principles -> framework -> commands -> agent - Role definitions now only exist in their respective command files - Creative techniques centralized in framework file - Agent focused solely on execution logic - Clear hierarchical reference structure without duplication 🤖 Generated with Claude Code Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -36,7 +36,7 @@ Business process expert responsible for analyzing workflows, identifying require
|
|||||||
## 🧠 **Analysis Framework**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### Key Analysis Questions
|
### Key Analysis Questions
|
||||||
|
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ Strategic data professional responsible for designing scalable, efficient data a
|
|||||||
## 🧠 **Analysis Framework**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### Key Analysis Questions
|
### Key Analysis Questions
|
||||||
|
|
||||||
|
|||||||
@@ -27,7 +27,7 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
|||||||
## 🧠 **分析框架**
|
## 🧠 **分析框架**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### 核心分析问题
|
### 核心分析问题
|
||||||
1. **功能需求分析**:
|
1. **功能需求分析**:
|
||||||
|
|||||||
@@ -24,10 +24,10 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
|||||||
- **创新机会**: 破坏性创新、蓝海市场、技术融合机会
|
- **创新机会**: 破坏性创新、蓝海市场、技术融合机会
|
||||||
- **未来愿景**: 长期技术路线图、概念验证、原型开发
|
- **未来愿景**: 长期技术路线图、概念验证、原型开发
|
||||||
|
|
||||||
## 🧠 **分析框架**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### 核心分析问题
|
### 核心分析问题
|
||||||
1. **技术趋势和机会**:
|
1. **技术趋势和机会**:
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ Strategic product leader focused on maximizing user value and business impact th
|
|||||||
## 🧠 **Analysis Framework**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### Key Analysis Questions
|
### Key Analysis Questions
|
||||||
|
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ Cybersecurity specialist focused on identifying threats, designing security cont
|
|||||||
## 🧠 **Analysis Framework**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### Key Analysis Questions
|
### Key Analysis Questions
|
||||||
|
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ Technical leader responsible for designing scalable, maintainable, and high-perf
|
|||||||
## 🧠 **Analysis Framework**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### Key Analysis Questions
|
### Key Analysis Questions
|
||||||
|
|
||||||
|
|||||||
@@ -36,7 +36,7 @@ Creative professional responsible for designing intuitive, accessible, and visua
|
|||||||
## 🧠 **Analysis Framework**
|
## 🧠 **Analysis Framework**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### Key Analysis Questions
|
### Key Analysis Questions
|
||||||
|
|
||||||
|
|||||||
@@ -27,7 +27,7 @@ allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
|
|||||||
## 🧠 **分析框架**
|
## 🧠 **分析框架**
|
||||||
|
|
||||||
@~/.claude/workflows/brainstorming-principles.md
|
@~/.claude/workflows/brainstorming-principles.md
|
||||||
@~/.claude/workflows/conceptual-planning-agent.md
|
@~/.claude/workflows/brainstorming-framework.md
|
||||||
|
|
||||||
### 核心分析问题
|
### 核心分析问题
|
||||||
1. **用户理解和洞察**:
|
1. **用户理解和洞察**:
|
||||||
|
|||||||
169
.claude/workflows/brainstorming-framework.md
Normal file
169
.claude/workflows/brainstorming-framework.md
Normal file
@@ -0,0 +1,169 @@
|
|||||||
|
# Brainstorming Framework
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
Common creative techniques, execution modes, and quality standards for all brainstorming sessions.
|
||||||
|
|
||||||
|
## Creative Techniques
|
||||||
|
|
||||||
|
### SCAMPER Method
|
||||||
|
- **Substitute**: What can be substituted or replaced?
|
||||||
|
- **Combine**: What can be combined or merged?
|
||||||
|
- **Adapt**: What can be adapted from elsewhere?
|
||||||
|
- **Modify**: What can be magnified, minimized, or modified?
|
||||||
|
- **Put to other uses**: How else can this be used?
|
||||||
|
- **Eliminate**: What can be removed or simplified?
|
||||||
|
- **Reverse**: What can be rearranged or reversed?
|
||||||
|
|
||||||
|
### Six Thinking Hats
|
||||||
|
- **White Hat**: Facts, information, data
|
||||||
|
- **Red Hat**: Emotions, feelings, intuition
|
||||||
|
- **Black Hat**: Critical judgment, caution, problems
|
||||||
|
- **Yellow Hat**: Optimism, benefits, positive thinking
|
||||||
|
- **Green Hat**: Creativity, alternatives, new ideas
|
||||||
|
- **Blue Hat**: Process control, meta-thinking
|
||||||
|
|
||||||
|
### Additional Techniques
|
||||||
|
- **Mind Mapping**: Visual idea exploration and connection
|
||||||
|
- **Brainstorming**: Free-flowing idea generation
|
||||||
|
- **Brainwriting**: Silent idea generation and building
|
||||||
|
- **Random Word**: Stimulus-based creative thinking
|
||||||
|
- **What If**: Scenario-based exploration
|
||||||
|
- **Assumption Challenging**: Question fundamental assumptions
|
||||||
|
|
||||||
|
## Execution Modes
|
||||||
|
|
||||||
|
### Creative Mode (Default)
|
||||||
|
- **Techniques**: SCAMPER, Six Thinking Hats, wild ideas
|
||||||
|
- **Focus**: Innovation and unconventional solutions
|
||||||
|
- **Approach**:
|
||||||
|
- Emphasize divergent thinking and wild ideas
|
||||||
|
- Apply creative techniques extensively
|
||||||
|
- Encourage "what if" thinking and assumption challenging
|
||||||
|
- Focus on novel and unconventional solutions
|
||||||
|
|
||||||
|
### Analytical Mode
|
||||||
|
- **Techniques**: Root cause analysis, data-driven insights
|
||||||
|
- **Focus**: Evidence-based systematic problem-solving
|
||||||
|
- **Approach**:
|
||||||
|
- Use structured analysis frameworks
|
||||||
|
- Apply root cause analysis and logical thinking
|
||||||
|
- Emphasize evidence-based reasoning
|
||||||
|
- Focus on systematic problem-solving
|
||||||
|
|
||||||
|
### Strategic Mode
|
||||||
|
- **Techniques**: Systems thinking, scenario planning
|
||||||
|
- **Focus**: Long-term strategic positioning
|
||||||
|
- **Approach**:
|
||||||
|
- Apply strategic thinking frameworks
|
||||||
|
- Use systems thinking and long-term perspective
|
||||||
|
- Consider competitive dynamics and market forces
|
||||||
|
- Focus on strategic positioning and advantage
|
||||||
|
|
||||||
|
## Brainstorming Session Protocol
|
||||||
|
|
||||||
|
### Input Processing
|
||||||
|
```
|
||||||
|
Topic: [Challenge or opportunity description]
|
||||||
|
Mode: [creative|analytical|strategic]
|
||||||
|
Perspectives: [Selected role perspectives]
|
||||||
|
Context: [Current situation and constraints]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Execution Flow
|
||||||
|
```
|
||||||
|
1. Challenge Analysis → Define scope, constraints, success criteria
|
||||||
|
2. Perspective Setup → Establish role contexts and viewpoints
|
||||||
|
3. Ideation Phase → Generate ideas using appropriate techniques
|
||||||
|
4. Convergence Phase → Evaluate, synthesize, prioritize solutions
|
||||||
|
5. Documentation → Create structured session records
|
||||||
|
```
|
||||||
|
|
||||||
|
## Documentation Standards
|
||||||
|
|
||||||
|
### Session Summary Generation
|
||||||
|
Generate comprehensive session documentation including:
|
||||||
|
- Session metadata and configuration
|
||||||
|
- Challenge definition and scope
|
||||||
|
- Key insights and patterns
|
||||||
|
- Generated ideas with descriptions
|
||||||
|
- Perspective analysis from each role
|
||||||
|
- Evaluation and prioritization
|
||||||
|
- Recommendations and next steps
|
||||||
|
|
||||||
|
### Idea Documentation
|
||||||
|
For each significant idea, create detailed documentation:
|
||||||
|
- Concept description and core mechanism
|
||||||
|
- Multi-perspective analysis and implications
|
||||||
|
- Feasibility assessment (technical, resource, timeline)
|
||||||
|
- Impact potential (user, business, technical)
|
||||||
|
- Implementation considerations and prerequisites
|
||||||
|
- Success metrics and validation approach
|
||||||
|
- Risk assessment and mitigation strategies
|
||||||
|
|
||||||
|
## Output Format Standards
|
||||||
|
|
||||||
|
### Brainstorming Session Output
|
||||||
|
```
|
||||||
|
BRAINSTORMING_SUMMARY: [Comprehensive session overview]
|
||||||
|
CHALLENGE_DEFINITION: [Clear problem space definition]
|
||||||
|
KEY_INSIGHTS: [Major discoveries and patterns]
|
||||||
|
IDEA_INVENTORY: [Structured list of all generated ideas]
|
||||||
|
TOP_CONCEPTS: [5 most promising solutions with analysis]
|
||||||
|
PERSPECTIVE_SYNTHESIS: [Integration of role-based insights]
|
||||||
|
FEASIBILITY_ASSESSMENT: [Technical and resource evaluation]
|
||||||
|
IMPACT_ANALYSIS: [Expected outcomes and benefits]
|
||||||
|
RECOMMENDATIONS: [Prioritized next steps and actions]
|
||||||
|
WORKFLOW_INTEGRATION: [If applicable, workflow handoff preparation]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Multi-Role Analysis Output
|
||||||
|
```
|
||||||
|
ROLE_COORDINATION: [How perspectives were integrated]
|
||||||
|
PERSPECTIVE_INSIGHTS: [Key insights from each role]
|
||||||
|
SYNTHESIS_RESULTS: [Combined perspective analysis]
|
||||||
|
CONFLICT_RESOLUTION: [How role conflicts were addressed]
|
||||||
|
COMPREHENSIVE_COVERAGE: [Confirmation all aspects considered]
|
||||||
|
```
|
||||||
|
|
||||||
|
## Quality Standards
|
||||||
|
|
||||||
|
### Effective Session Facilitation
|
||||||
|
- **Clear Structure** → Follow defined phases and maintain session flow
|
||||||
|
- **Inclusive Participation** → Ensure all perspectives are heard and valued
|
||||||
|
- **Creative Environment** → Maintain judgment-free ideation atmosphere
|
||||||
|
- **Productive Tension** → Balance creativity with practical constraints
|
||||||
|
- **Actionable Outcomes** → Generate concrete next steps and recommendations
|
||||||
|
|
||||||
|
### Perspective Integration
|
||||||
|
- **Authentic Representation** → Accurately channel each role's mental models
|
||||||
|
- **Balanced Coverage** → Give appropriate attention to all perspectives
|
||||||
|
- **Constructive Synthesis** → Combine insights into stronger solutions
|
||||||
|
- **Conflict Navigation** → Address perspective tensions constructively
|
||||||
|
- **Comprehensive Analysis** → Ensure no critical aspects are overlooked
|
||||||
|
|
||||||
|
### Documentation Quality
|
||||||
|
- **Structured Capture** → Organize insights and ideas systematically
|
||||||
|
- **Clear Communication** → Present complex ideas in accessible format
|
||||||
|
- **Decision Support** → Provide frameworks for evaluating options
|
||||||
|
- **Implementation Ready** → Prepare outputs for next development phases
|
||||||
|
- **Traceability** → Maintain clear links between ideas and analysis
|
||||||
|
|
||||||
|
## Integration Guidelines
|
||||||
|
|
||||||
|
### With Brainstorming Principles
|
||||||
|
This framework works in conjunction with @~/.claude/workflows/brainstorming-principles.md which defines:
|
||||||
|
- Project structure establishment
|
||||||
|
- Session initialization requirements
|
||||||
|
- Directory creation protocols
|
||||||
|
- Agent coordination standards
|
||||||
|
|
||||||
|
### With Role Commands
|
||||||
|
Each role-specific brainstorm command implements this framework within their domain context:
|
||||||
|
- Applies appropriate techniques for their perspective
|
||||||
|
- Uses mode selection based on problem type
|
||||||
|
- Follows documentation standards
|
||||||
|
- Maintains quality criteria
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
This framework provides the common foundation for all brainstorming activities while allowing role-specific customization and focus.
|
||||||
@@ -4,139 +4,48 @@
|
|||||||
**Integration Principles**: See @~/.claude/workflows/brainstorming-principles.md
|
**Integration Principles**: See @~/.claude/workflows/brainstorming-principles.md
|
||||||
|
|
||||||
## Purpose
|
## Purpose
|
||||||
Multi-role brainstorming and conceptual planning agent specialized in creative problem-solving, strategic thinking, and comprehensive perspective coordination.
|
Agent for executing single-role conceptual planning and brainstorming analysis based on assigned perspectives.
|
||||||
|
|
||||||
## Core Capabilities
|
## Core Capabilities
|
||||||
|
- **Single-Role Analysis** → Deep analysis from one assigned role perspective
|
||||||
### Brainstorming Facilitation
|
- **Context Integration** → Incorporate user requirements and constraints
|
||||||
- **Multi-Perspective Coordination** → Orchestrate insights from different role perspectives
|
- **Documentation Generation** → Create role-specific analysis outputs
|
||||||
- **Creative Technique Application** → Apply SCAMPER, Six Thinking Hats, and other proven methods
|
- **Framework Application** → Apply techniques from @~/.claude/workflows/brainstorming-framework.md
|
||||||
- **Structured Ideation** → Guide systematic idea generation and evaluation processes
|
|
||||||
- **Session Documentation** → Create comprehensive brainstorming records and summaries
|
|
||||||
|
|
||||||
### Strategic Analysis
|
|
||||||
- **Systems Thinking** → Analyze complex interdependencies and relationships
|
|
||||||
- **Scenario Planning** → Explore multiple future possibilities and outcomes
|
|
||||||
- **Strategic Framework Application** → Use established strategic analysis tools
|
|
||||||
- **Long-term Vision Development** → Create compelling future state visions
|
|
||||||
|
|
||||||
### Multi-Role Perspective Integration
|
|
||||||
- **Role-Based Analysis** → Channel different expertise areas and mental models
|
|
||||||
- **Perspective Synthesis** → Combine insights from multiple viewpoints into coherent solutions
|
|
||||||
- **Conflict Resolution** → Address tensions between different role perspectives
|
|
||||||
- **Comprehensive Coverage** → Ensure all relevant aspects are considered
|
|
||||||
|
|
||||||
## Execution Patterns
|
## Execution Patterns
|
||||||
|
|
||||||
### Brainstorming Session Protocol
|
### Agent Invocation
|
||||||
|
This agent is called by role-specific brainstorm commands with:
|
||||||
|
- **ASSIGNED_ROLE**: The specific role to embody
|
||||||
|
- **Topic**: Challenge or opportunity to analyze
|
||||||
|
- **Context**: User requirements and constraints
|
||||||
|
- **Output Location**: Where to save analysis files
|
||||||
|
|
||||||
**Input Processing**:
|
### Execution Flow
|
||||||
```
|
See @~/.claude/workflows/brainstorming-framework.md for detailed execution patterns and techniques.
|
||||||
Topic: [Challenge or opportunity description]
|
|
||||||
Mode: [creative|analytical|strategic]
|
|
||||||
Perspectives: [Selected role perspectives]
|
|
||||||
Context: [Current situation and constraints]
|
|
||||||
```
|
|
||||||
|
|
||||||
**Execution Flow**:
|
### Role References
|
||||||
```
|
|
||||||
1. Challenge Analysis → Define scope, constraints, success criteria
|
|
||||||
2. Perspective Setup → Establish role contexts and viewpoints
|
|
||||||
3. Ideation Phase → Generate ideas using appropriate techniques
|
|
||||||
4. Convergence Phase → Evaluate, synthesize, prioritize solutions
|
|
||||||
5. Documentation → Create structured session records
|
|
||||||
```
|
|
||||||
|
|
||||||
### Multi-Role Perspective Execution
|
**Available Roles**: Each role has its own command file with detailed definitions:
|
||||||
|
- `business-analyst` - See `.claude/commands/workflow/brainstorm/business-analyst.md`
|
||||||
|
- `data-architect` - See `.claude/commands/workflow/brainstorm/data-architect.md`
|
||||||
|
- `feature-planner` - See `.claude/commands/workflow/brainstorm/feature-planner.md`
|
||||||
|
- `innovation-lead` - See `.claude/commands/workflow/brainstorm/innovation-lead.md`
|
||||||
|
- `product-manager` - See `.claude/commands/workflow/brainstorm/product-manager.md`
|
||||||
|
- `security-expert` - See `.claude/commands/workflow/brainstorm/security-expert.md`
|
||||||
|
- `system-architect` - See `.claude/commands/workflow/brainstorm/system-architect.md`
|
||||||
|
- `ui-designer` - See `.claude/commands/workflow/brainstorm/ui-designer.md`
|
||||||
|
- `user-researcher` - See `.claude/commands/workflow/brainstorm/user-researcher.md`
|
||||||
|
|
||||||
**Available Roles and Contexts**:
|
### Creative Techniques
|
||||||
|
|
||||||
**Product Manager Perspective**:
|
For detailed creative techniques including SCAMPER, Six Thinking Hats, and other methods, see:
|
||||||
- Focus: User needs, business value, market positioning
|
@~/.claude/workflows/brainstorming-framework.md#creative-techniques
|
||||||
- Questions: What do users want? How does this create business value?
|
|
||||||
- Output: User stories, business cases, market analysis
|
|
||||||
|
|
||||||
**System Architect Perspective**:
|
### Execution Modes
|
||||||
- Focus: Technical architecture, scalability, integration
|
|
||||||
- Questions: How does this scale? What are technical constraints?
|
|
||||||
- Output: Architecture diagrams, technical requirements, system design
|
|
||||||
|
|
||||||
**UI Designer Perspective**:
|
For detailed execution modes (Creative, Analytical, Strategic), see:
|
||||||
- Focus: User experience, interface design, usability
|
@~/.claude/workflows/brainstorming-framework.md#execution-modes
|
||||||
- Questions: How do users interact? What's the optimal user journey?
|
|
||||||
- Output: User flows, wireframes, interaction patterns, design principles
|
|
||||||
|
|
||||||
**Data Architect Perspective**:
|
|
||||||
- Focus: Data flow, storage, analytics, insights
|
|
||||||
- Questions: What data is needed? How is it processed and analyzed?
|
|
||||||
- Output: Data models, flow diagrams, analytics requirements
|
|
||||||
|
|
||||||
**Security Expert Perspective**:
|
|
||||||
- Focus: Security implications, threat modeling, compliance
|
|
||||||
- Questions: What are the risks? How do we protect against threats?
|
|
||||||
- Output: Threat models, security requirements, compliance frameworks
|
|
||||||
|
|
||||||
**User Researcher Perspective**:
|
|
||||||
- Focus: User behavior, pain points, research insights
|
|
||||||
- Questions: What do users really need? What problems are we solving?
|
|
||||||
- Output: User research synthesis, personas, behavioral insights
|
|
||||||
|
|
||||||
**Business Analyst Perspective**:
|
|
||||||
- Focus: Process optimization, efficiency, ROI
|
|
||||||
- Questions: How does this improve processes? What's the return on investment?
|
|
||||||
- Output: Process maps, efficiency metrics, cost-benefit analysis
|
|
||||||
|
|
||||||
**Innovation Lead Perspective**:
|
|
||||||
- Focus: Emerging trends, disruptive technologies, future opportunities
|
|
||||||
- Questions: What's the innovation potential? What trends are relevant?
|
|
||||||
- Output: Technology roadmaps, trend analysis, innovation opportunities
|
|
||||||
|
|
||||||
### Creative Technique Application
|
|
||||||
|
|
||||||
**SCAMPER Method**:
|
|
||||||
- **Substitute**: What can be substituted or replaced?
|
|
||||||
- **Combine**: What can be combined or merged?
|
|
||||||
- **Adapt**: What can be adapted from elsewhere?
|
|
||||||
- **Modify**: What can be magnified, minimized, or modified?
|
|
||||||
- **Put to other uses**: How else can this be used?
|
|
||||||
- **Eliminate**: What can be removed or simplified?
|
|
||||||
- **Reverse**: What can be rearranged or reversed?
|
|
||||||
|
|
||||||
**Six Thinking Hats**:
|
|
||||||
- **White Hat**: Facts, information, data
|
|
||||||
- **Red Hat**: Emotions, feelings, intuition
|
|
||||||
- **Black Hat**: Critical judgment, caution, problems
|
|
||||||
- **Yellow Hat**: Optimism, benefits, positive thinking
|
|
||||||
- **Green Hat**: Creativity, alternatives, new ideas
|
|
||||||
- **Blue Hat**: Process control, meta-thinking
|
|
||||||
|
|
||||||
**Additional Techniques**:
|
|
||||||
- **Mind Mapping**: Visual idea exploration and connection
|
|
||||||
- **Brainstorming**: Free-flowing idea generation
|
|
||||||
- **Brainwriting**: Silent idea generation and building
|
|
||||||
- **Random Word**: Stimulus-based creative thinking
|
|
||||||
- **What If**: Scenario-based exploration
|
|
||||||
- **Assumption Challenging**: Question fundamental assumptions
|
|
||||||
|
|
||||||
### Mode-Specific Execution
|
|
||||||
|
|
||||||
**Creative Mode**:
|
|
||||||
- Emphasize divergent thinking and wild ideas
|
|
||||||
- Apply creative techniques extensively
|
|
||||||
- Encourage "what if" thinking and assumption challenging
|
|
||||||
- Focus on novel and unconventional solutions
|
|
||||||
|
|
||||||
**Analytical Mode**:
|
|
||||||
- Use structured analysis frameworks
|
|
||||||
- Apply root cause analysis and logical thinking
|
|
||||||
- Emphasize evidence-based reasoning
|
|
||||||
- Focus on systematic problem-solving
|
|
||||||
|
|
||||||
**Strategic Mode**:
|
|
||||||
- Apply strategic thinking frameworks
|
|
||||||
- Use systems thinking and long-term perspective
|
|
||||||
- Consider competitive dynamics and market forces
|
|
||||||
- Focus on strategic positioning and advantage
|
|
||||||
|
|
||||||
## Documentation Standards
|
## Documentation Standards
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user