mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-13 02:41:50 +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:
catlog22
@@ -4,139 +4,48 @@
|
||||
**Integration Principles**: See @~/.claude/workflows/brainstorming-principles.md
|
||||
|
||||
## 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
|
||||
|
||||
### Brainstorming Facilitation
|
||||
- **Multi-Perspective Coordination** → Orchestrate insights from different role perspectives
|
||||
- **Creative Technique Application** → Apply SCAMPER, Six Thinking Hats, and other proven methods
|
||||
- **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
|
||||
- **Single-Role Analysis** → Deep analysis from one assigned role perspective
|
||||
- **Context Integration** → Incorporate user requirements and constraints
|
||||
- **Documentation Generation** → Create role-specific analysis outputs
|
||||
- **Framework Application** → Apply techniques from @~/.claude/workflows/brainstorming-framework.md
|
||||
|
||||
## 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**:
|
||||
```
|
||||
Topic: [Challenge or opportunity description]
|
||||
Mode: [creative|analytical|strategic]
|
||||
Perspectives: [Selected role perspectives]
|
||||
Context: [Current situation and constraints]
|
||||
```
|
||||
### Execution Flow
|
||||
See @~/.claude/workflows/brainstorming-framework.md for detailed execution patterns and techniques.
|
||||
|
||||
**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
|
||||
```
|
||||
### Role References
|
||||
|
||||
### 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**:
|
||||
- Focus: User needs, business value, market positioning
|
||||
- Questions: What do users want? How does this create business value?
|
||||
- Output: User stories, business cases, market analysis
|
||||
For detailed creative techniques including SCAMPER, Six Thinking Hats, and other methods, see:
|
||||
@~/.claude/workflows/brainstorming-framework.md#creative-techniques
|
||||
|
||||
**System Architect Perspective**:
|
||||
- Focus: Technical architecture, scalability, integration
|
||||
- Questions: How does this scale? What are technical constraints?
|
||||
- Output: Architecture diagrams, technical requirements, system design
|
||||
### Execution Modes
|
||||
|
||||
**UI Designer Perspective**:
|
||||
- Focus: User experience, interface design, usability
|
||||
- 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
|
||||
For detailed execution modes (Creative, Analytical, Strategic), see:
|
||||
@~/.claude/workflows/brainstorming-framework.md#execution-modes
|
||||
|
||||
## Documentation Standards
|
||||
|
||||
|
||||
Reference in New Issue
Block a user