catlog22/Claude-Code-Workflow
1
0
Fork 0
mirror of https://github.com/catlog22/Claude-Code-Workflow.git synced 2026-02-05 01:50:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

Add comprehensive brainstorming commands for synthesis, system architecture, UI design, and user research perspectives

Browse Source 
- Implemented the `brainstorm:synthesis` command to integrate insights from various roles into a cohesive analysis and recommendations report.
- Created `brainstorm:system-architect` command for technical architecture and scalability analysis, including detailed execution protocols and output structures.
- Developed `brainstorm:ui-designer` command focusing on user experience and interface design, with a structured approach to analysis and documentation.
- Introduced `brainstorm:user-researcher` command for user behavior analysis and research insights, emphasizing user needs and usability assessments.
This commit is contained in:
catlog22
2025-09-08 23:35:23 +08:00
parent 1454c49ab0
commit d643a59307
11 changed files with 2568 additions and 506 deletions
Download Patch File Download Diff File Expand all files Collapse all files

506
.claude/commands/workflow/brainstorm.md
View File

@@ -1,506 +0,0 @@
---
name: brainstorm
description: Multi-perspective brainstorming coordination command that orchestrates multiple agents for comprehensive ideation and solution exploration
usage: /brainstorm <topic|challenge> [--mode=<creative|analytical|strategic>] [--perspectives=<role1,role2,...>] [--execution=<serial|parallel>]
argument-hint: "brainstorming topic or challenge description" [optional: mode, perspectives, execution]
examples:
- /brainstorm "innovative user authentication methods"
- /brainstorm "solving scalability challenges" --mode=analytical
- /brainstorm "redesigning the onboarding experience" --perspectives=ui-designer,user-researcher,product-manager
- /brainstorm "reducing system complexity" --mode=strategic --execution=parallel
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
### 🚀 **Command Overview: `/brainstorm`**
- **Type**: Coordination Command
- **Purpose**: To orchestrate multiple specialized agents for comprehensive multi-perspective brainstorming on challenges and opportunities.
- **Core Tools**: `Task(conceptual-planning-agent)`, `TodoWrite(*)`
- **Integration Rules**: @~/.claude/workflows/brainstorming-principles.md
### 🔄 **Overall Brainstorming Protocol**
`Phase 1: Coordination Setup` **->** `Phase 1.5: User Discussion & Validation` **->** `Phase 2: Agent Coordination` **->** `Phase 3: Synthesis & Documentation`
### ⚙️ **Brainstorming Modes**
- **`creative` (Default)**
- **Approach**: Divergent thinking, "what if" scenarios.
- **Agent Selection**: Auto-selects `innovation-lead`, `ui-designer`, `user-researcher`, and a business agent.
- **Execution**: Typically parallel.
- **`analytical`**
- **Approach**: Root cause analysis, data-driven insights.
- **Agent Selection**: Auto-selects `business-analyst`, `data-architect`, `system-architect`, and a domain expert.
- **Execution**: Typically serial.
- **`strategic`**
- **Approach**: Systems thinking, long-term visioning.
- **Agent Selection**: Auto-selects `innovation-lead`, `product-manager`, `business-analyst`, and a technical expert.
- **Execution**: Mixed serial/parallel.
### 🚦 **Execution Patterns**
- **`serial` (Default)**
- **Use Case**: When perspectives need to build on each other.
- **Process**: Agents run one at a time, informed by previous outputs.
- **`parallel`**
- **Use Case**: When diverse, independent perspectives are needed quickly.
- **Process**: All selected agents run simultaneously.
- **`hybrid`**
- **Use Case**: Complex, multi-phase brainstorming.
- **Process**: Combines parallel initial ideation with serial refinement phases.
### 🎭 **Available Perspectives (Agent Roles)**
- `product-manager`: User needs, business value, market positioning.
- `system-architect`: Technical architecture, scalability, integration.
- `ui-designer`: User experience, interface design, usability.
- `data-architect`: Data flow, storage, analytics, insights.
- `security-expert`: Security implications, threat modeling, compliance.
- `user-researcher`: User behavior, pain points, research insights.
- `business-analyst`: Process optimization, efficiency, ROI.
- `innovation-lead`: Emerging trends, disruptive technologies, opportunities.
- `feature-planner`: Feature planning and development strategy.
- `test-strategist`: Testing strategy and quality assurance.
### 🤖 **Agent Selection & Loading Logic**
This logic determines which agents participate in the brainstorming session.
```pseudo
FUNCTION select_agents(mode, perspectives_arg):
IF perspectives_arg is provided:
// User explicitly defines roles via --perspectives flag
RETURN perspectives_arg.split(',')
ELSE:
// Automatic selection based on mode or topic analysis
CASE topic_type:
WHEN "Technical Challenge":
selected = ["system-architect", "security-expert"]
IF topic is data_heavy: ADD "data-architect"
RETURN selected
WHEN "User-Facing Feature":
RETURN ["ui-designer", "user-researcher", "product-manager"]
WHEN "Business Process":
RETURN ["business-analyst", "product-manager"]
WHEN "Innovation/Strategy":
RETURN ["innovation-lead", "product-manager"]
DEFAULT:
// Fallback to mode-based selection
CASE mode:
WHEN "creative": RETURN ["innovation-lead", "ui-designer", "user-researcher", ...]
WHEN "analytical": RETURN ["business-analyst", "data-architect", "system-architect", ...]
WHEN "strategic": RETURN ["innovation-lead", "product-manager", "business-analyst", ...]
END CASE
END CASE
END IF
END FUNCTION
FUNCTION load_agent_role(role_name):
// Dynamically loads role capabilities using the specified shell script
execute_tool("Bash", "~/.claude/scripts/plan-executor.sh " + role_name)
END FUNCTION
```
### 🏗️ **Phase 1: Coordination Setup Protocol**
⚠️ **CRITICAL**: Before brainstorming, MUST check for existing active session to avoid creating duplicate sessions.
**Session Check Process:**
1. **Check Active Session**: Check for `.workflow/.active-*` marker file to identify active session. No file creation needed.
2. **Session Selection**: Use existing active session or create new one only if none exists
3. **Context Integration**: Load existing session state and continue brainstorming phase
`Check Active Session` **->** `Generate Topic Slug (WFS-[topic-slug]) if needed` **->** `Create Project Directories (.workflow/WFS-[slug]/.brainstorming/{agent1}, {agent2}, ...)` **->** `Initialize/Update session-state.json` **->** `Verify Structure` **->** `Initialize TodoWrite`
### 📝 **Initial TodoWrite Structure (Template)**
This `TodoWrite` call establishes the complete workflow plan at the beginning of the session.
```
TodoWrite([
{"content": "Establish project structure and initialize session", "status": "completed", "activeForm": "Establishing project structure"},
{"content": "Set up brainstorming session and select perspectives", "status": "in_progress", "activeForm": "Setting up brainstorming session"},
{"content": "Discuss [agent1] scope and gather user requirements", "status": "pending", "activeForm": "Discussing [agent1] requirements with user"},
{"content": "Coordinate [selected_agent1] perspective analysis", "status": "pending", "activeForm": "Coordinating [agent1] perspective"},
{"content": "Discuss [agent2] scope and gather user requirements", "status": "pending", "activeForm": "Discussing [agent2] requirements with user"},
{"content": "Coordinate [selected_agent2] perspective analysis", "status": "pending", "activeForm": "Coordinating [agent2] perspective"},
{"content": "Discuss [agent3] scope and gather user requirements", "status": "pending", "activeForm": "Discussing [agent3] requirements with user"},
{"content": "Coordinate [selected_agent3] perspective analysis", "status": "pending", "activeForm": "Coordinating [agent3] perspective"},
{"content": "Synthesize multi-perspective insights", "status": "pending", "activeForm": "Synthesizing insights"},
{"content": "Generate prioritized recommendations", "status": "pending", "activeForm": "Generating recommendations"},
{"content": "Create comprehensive brainstorming documentation", "status": "pending", "activeForm": "Creating documentation"}
])
```
### 💬 **Phase 1.5: Mandatory User Discussion Protocol**
This validation loop is **required** before *each* agent is executed.
```pseudo
FUNCTION validate_and_run_agents(selected_agents):
FOR EACH agent in selected_agents:
// Update the task list to show which discussion is active
update_todowrite("Discuss " + agent + " scope", "in_progress") // Corresponds to TodoWrite(*) tool
present_agent_scope(agent)
user_context = ask_context_questions(agent) // Example questions in next card
present_task_roadmap(agent)
LOOP:
user_response = get_user_input("Ready to proceed with " + agent + " analysis?")
IF user_response is "Yes, proceed" or similar:
// User has given explicit approval
update_todowrite("Discuss " + agent + " scope", "completed") // Corresponds to TodoWrite(*)
execute_agent_task(agent, user_context) // Proceeds to Phase 2 for this agent
BREAK
ELSE IF user_response is "No", "Wait", or requests changes:
// User has feedback, revise the plan
revise_approach(user_feedback)
present_task_roadmap(agent) // Re-present the revised plan
END IF
END LOOP
END FOR
END FUNCTION
```
### ❓ **User Discussion Question Templates**
- **System Architect**: Technical constraints? Integrations? Scalability needs?
- **UI Designer**: Primary users? Usability challenges? Brand guidelines? Accessibility?
- **Product Manager**: Business goals? Key stakeholders? Market factors? Success metrics?
- **Data Architect**: Data sources? Privacy/compliance? Quality challenges?
- **Security Expert**: Threat models? Compliance needs (GDPR, etc.)? Security level?
### 🧠 **Phase 2: Agent Coordination Logic**
This logic executes after user approval for each agent.
```pseudo
FUNCTION execute_agent_task(agent, user_context):
update_todowrite("Coordinate " + agent + " perspective", "in_progress") // Corresponds to TodoWrite(*) tool
// This action corresponds to calling the allowed tool: Task(conceptual-planning-agent)
// The specific prompt templates are provided in the source documentation.
status = execute_tool("Task(conceptual-planning-agent)", agent, user_context)
IF status is 'SUCCESS':
update_todowrite("Coordinate " + agent + " perspective", "completed")
ELSE:
// Handle potential agent execution failure
log_error("Agent " + agent + " failed.")
HALT_WORKFLOW()
END IF
END FUNCTION
```
### 📋 **Agent Execution Task Templates (Serial & Parallel)**
These templates show the exact structure of the `Task(conceptual-planning-agent)` call.
- **For Serial Execution (one agent at a time):**
```
Task(conceptual-planning-agent): "Conduct brainstorming analysis for: [topic]. Use [mode] brainstorming approach. Required perspective: [agent1].
Load role definition using: ~/.claude/scripts/plan-executor.sh [agent1]
USER CONTEXT FROM DISCUSSION:
- Specific focus areas: [user_specified_challenges_goals]
- Constraints and requirements: [user_specified_constraints]
- Expected outcomes: [user_expected_outcomes]
- Additional user requirements: [other_user_inputs]
OUTPUT REQUIREMENT: Save all generated documents to: .workflow/WFS-[topic-slug]/.brainstorming/[agent1]/
- analysis.md (main perspective analysis incorporating user context)
- [agent1-specific-output].md (specialized deliverable addressing user requirements)
Apply the returned planning template and generate comprehensive analysis from this perspective, ensuring all user-specified requirements and context are fully incorporated."
```
- **For Parallel Execution (multiple agents at once):**
```
Task(conceptual-planning-agent): "Conduct multi-perspective brainstorming analysis for: [topic]. Use [mode] brainstorming approach. Required perspectives: [agent1, agent2, agent3].
For each perspective, follow this protocol:
1. Load role definition using: ~/.claude/scripts/plan-executor.sh [role]
2. Incorporate user discussion context for each agent:
- [Agent1]: Focus areas: [user_input_agent1], Constraints: [constraints_agent1], Expected outcomes: [outcomes_agent1]
- [Agent2]: Focus areas: [user_input_agent2], Constraints: [constraints_agent2], Expected outcomes: [outcomes_agent2]
- [Agent3]: Focus areas: [user_input_agent3], Constraints: [constraints_agent3], Expected outcomes: [outcomes_agent3]
3. OUTPUT REQUIREMENT: Save documents to: .workflow/WFS-[topic-slug]/.brainstorming/[role]/
- analysis.md (main perspective analysis incorporating user context)
- [role-specific-output].md (specialized deliverable addressing user requirements)
Apply all perspectives in parallel analysis, ensuring each agent's output incorporates their specific user discussion context and is saved to their designated directory."
```
### 🏁 **Phase 3: Synthesis & Documentation Flow**
`Integrate All Agent Insights` **->** `Prioritize Solutions (by feasibility & impact)` **->** `Generate Comprehensive Summary Document` **->** `Mark All Todos as 'completed'`
### ✅ **Core Principles & Quality Standards**
- **User-Driven Process**: Every agent execution **must** be preceded by user discussion and explicit approval.
- **Context Integration**: All user inputs (focus areas, constraints, goals) must be fully incorporated into agent analysis.
- **`TodoWrite` First**: A `TodoWrite` plan must be established before any agent coordination begins.
- **Single Active Task**: Only one `TodoWrite` item should be marked `"in_progress"` at any time.
- **Transparent & Flexible**: The user understands what each agent will do and can provide feedback to revise the plan.
### 📄 **Synthesis Output Structure**
A guide for the final comprehensive report generated at the end of the workflow.
- **Session Summary**:
- Coordination approach (serial/parallel)
- Agent perspectives involved
- Brainstorming mode applied
- **Individual Agent Insights**:
- Summary of each agent's analysis.
- Note areas of agreement or disagreement.
- **Cross-Perspective Synthesis**:
- Identify convergent themes and breakthrough ideas.
- **Actionable Recommendations**:
- Categorize actions (immediate, strategic, research).
- **Implementation Guidance**:
- Suggested phases, resource needs, success metrics.
## 📁 **File Generation System**
### Automatic File Generation
Every brainstorming session generates a comprehensive set of structured output files:
#### Generated File Structure
```
.workflow/WFS-[topic-slug]/.brainstorming/
├── synthesis-analysis.md # Cross-perspective analysis
├── recommendations.md # Actionable recommendations
├── brainstorm-session.json # Session metadata
├── [agent1]/ # Individual agent outputs
│ ├── analysis.md # Main perspective analysis
│ └── [specific-deliverable].md # Agent-specific outputs
├── [agent2]/
│ ├── analysis.md
│ └── [specific-deliverable].md
└── artifacts/ # Supporting materials
├── user-context.md # Captured user discussion
├── session-transcript.md # Brainstorming session log
└── export/ # Export formats
├── brainstorm-summary.pdf
└── recommendations.json
```
### Core Output Documents
#### 1. synthesis-analysis.md
Cross-perspective synthesis of all agent insights:
```markdown
# Brainstorming Synthesis Analysis
*Session: WFS-[topic-slug] | Generated: 2025-09-07 16:00:00*
## Session Overview
- **Topic**: [brainstorming topic]
- **Mode**: [creative|analytical|strategic]
- **Execution**: [serial|parallel]
- **Participants**: [list of agent roles]
- **Duration**: [session duration]
## Individual Agent Insights Summary
### 🎨 UI Designer Perspective
**Focus Areas**: User experience, interface design, usability
**Key Insights**:
- Modern, intuitive design approach
- Mobile-first considerations
- Accessibility requirements
**Recommendations**: [specific design recommendations]
### 🏗️ System Architect Perspective
**Focus Areas**: Technical architecture, scalability, integration
**Key Insights**:
- Microservices architecture benefits
- Database optimization strategies
- Security considerations
**Recommendations**: [specific technical recommendations]
[Additional agent perspectives...]
## Cross-Perspective Analysis
### Convergent Themes
1. **User-Centric Approach**: All agents emphasized user experience priority
2. **Scalability Focus**: Common concern for system growth capacity
3. **Security Integration**: Unanimous priority on security-by-design
### Breakthrough Ideas
1. **Unified Authentication System**: Cross-platform identity management
2. **Progressive Web App**: Mobile and desktop feature parity
3. **AI-Powered Analytics**: Smart user behavior insights
### Areas of Disagreement
1. **Technology Stack**: [description of disagreement and perspectives]
2. **Implementation Timeline**: [varying estimates and approaches]
## Strategic Synthesis
[Integrated analysis combining all perspectives into coherent strategy]
---
*Generated by /brainstorm synthesis phase*
```
#### 2. recommendations.md
Actionable recommendations categorized by priority and scope:
```markdown
# Brainstorming Recommendations
*Session: WFS-[topic-slug] | Generated: 2025-09-07 16:15:00*
## Executive Summary
[High-level summary of key recommendations]
## Immediate Actions (0-2 weeks)
### High Priority - Critical
- **REC-001**: [Recommendation title]
- **Context**: [Background and rationale]
- **Action**: [Specific steps to take]
- **Resources**: [Required resources/skills]
- **Impact**: [Expected outcomes]
- **Owner**: [Suggested responsible party]
### Medium Priority - Important
- **REC-002**: [Recommendation title]
[Same structure as above]
## Strategic Actions (2-8 weeks)
### Architecture & Infrastructure
- **REC-003**: [Technical improvements]
- **REC-004**: [System optimizations]
### User Experience & Design
- **REC-005**: [UX improvements]
- **REC-006**: [Design system updates]
## Research Actions (Future Investigation)
### Technical Research
- **REC-007**: [Emerging technology evaluation]
- **REC-008**: [Performance optimization study]
### Market Research
- **REC-009**: [User behavior analysis]
- **REC-010**: [Competitive analysis]
## Implementation Roadmap
### Phase 1: Foundation (Weeks 1-2)
- Execute REC-001, REC-002
- Establish core infrastructure
### Phase 2: Development (Weeks 3-6)
- Implement REC-003, REC-004, REC-005
- Build core features
### Phase 3: Enhancement (Weeks 7-8)
- Deploy REC-006
- Optimize and refine
## Success Metrics
- [Quantifiable measures of success]
- [Key performance indicators]
## Risk Assessment
- [Potential obstacles and mitigation strategies]
---
*Generated by /brainstorm recommendations synthesis*
```
#### 3. brainstorm-session.json
Session metadata and tracking:
```json
{
"session_id": "WFS-[topic-slug]",
"brainstorm_id": "BRM-2025-09-07-001",
"topic": "[brainstorming topic]",
"mode": "creative",
"execution": "parallel",
"created_at": "2025-09-07T15:30:00Z",
"completed_at": "2025-09-07T16:30:00Z",
"duration_minutes": 60,
"participants": {
"agents": ["ui-designer", "system-architect", "product-manager"],
"user_interaction": true
},
"outputs": {
"agent_analyses": {
"ui-designer": {
"analysis_path": ".brainstorming/ui-designer/analysis.md",
"deliverable_path": ".brainstorming/ui-designer/design-mockups.md",
"completed_at": "2025-09-07T15:50:00Z"
},
"system-architect": {
"analysis_path": ".brainstorming/system-architect/analysis.md",
"deliverable_path": ".brainstorming/system-architect/architecture-proposal.md",
"completed_at": "2025-09-07T15:55:00Z"
},
"product-manager": {
"analysis_path": ".brainstorming/product-manager/analysis.md",
"deliverable_path": ".brainstorming/product-manager/feature-roadmap.md",
"completed_at": "2025-09-07T16:00:00Z"
}
},
"synthesis": {
"analysis_path": "synthesis-analysis.md",
"recommendations_path": "recommendations.md",
"completed_at": "2025-09-07T16:30:00Z"
}
},
"user_context": {
"focus_areas": "[captured from user discussion]",
"constraints": "[user-specified limitations]",
"expected_outcomes": "[user goals and expectations]"
},
"metrics": {
"insights_generated": 24,
"recommendations_count": 10,
"breakthrough_ideas": 3,
"consensus_areas": 3,
"disagreement_areas": 2
}
}
```
### Session Integration
After brainstorming completion, the main workflow-session.json is updated:
```json
{
"phases": {
"BRAINSTORM": {
"status": "completed",
"completed_at": "2025-09-07T16:30:00Z",
"output_directory": ".workflow/WFS-[topic-slug]/.brainstorming/",
"documents_generated": [
"synthesis-analysis.md",
"recommendations.md",
"brainstorm-session.json"
],
"agents_participated": ["ui-designer", "system-architect", "product-manager"],
"insights_available": true
}
},
"documents": {
"brainstorming": {
"synthesis-analysis.md": {
"status": "generated",
"path": ".workflow/WFS-[topic-slug]/.brainstorming/synthesis-analysis.md",
"generated_at": "2025-09-07T16:30:00Z",
"type": "synthesis_analysis"
},
"recommendations.md": {
"status": "generated",
"path": ".workflow/WFS-[topic-slug]/.brainstorming/recommendations.md",
"generated_at": "2025-09-07T16:30:00Z",
"type": "actionable_recommendations"
}
}
}
}
```
### Export and Integration Features
- **PDF Export**: Automatic generation of consolidated brainstorming report
- **JSON Export**: Machine-readable recommendations for integration tools
- **Action Plan Integration**: Direct feeding into `/workflow:action-plan --from-brainstorming`
- **Cross-Referencing**: Links to specific agent insights from synthesis documents

263
.claude/commands/workflow/brainstorm/business-analyst.md Normal file
View File

@@ -0,0 +1,263 @@
---
name: brainstorm:business-analyst
description: Business analyst perspective brainstorming for process optimization and business efficiency analysis
usage: /brainstorm:business-analyst <topic>
argument-hint: "topic or challenge to analyze from business analysis perspective"
examples:
- /brainstorm:business-analyst "workflow automation opportunities"
- /brainstorm:business-analyst "business process optimization"
- /brainstorm:business-analyst "cost reduction initiatives"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 📊 **角色定义: Business Analyst**
### 核心职责
- **流程分析**: 分析现有业务流程的效率和改进机会
- **需求分析**: 识别和定义业务需求和功能要求
- **效益评估**: 评估解决方案的商业价值和投资回报
- **变更管理**: 规划和管理业务流程变更
### 关注领域
- **流程优化**: 工作流程、自动化机会、效率提升
- **数据分析**: 业务指标、KPI设计、性能测量
- **成本效益**: ROI分析、成本优化、价值创造
- **风险管理**: 业务风险、合规要求、变更风险
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **业务流程分析**:
- 当前业务流程的瓶颈和低效环节？
- 哪些流程可以自动化或简化？
- 跨部门协作中的障碍点？
2. **业务需求识别**:
- 利益相关者的核心需求？
- 业务目标和成功指标？
- 功能和非功能需求优先级？
3. **价值和效益分析**:
- 解决方案的预期商业价值？
- 实施成本vs收益对比？
- 风险评估和缓解策略？
4. **实施和变更管理**:
- 变更对现有流程的影响？
- 培训和适应需求？
- 成功指标和监控机制？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建业务分析师分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/business-analyst/
```
### Phase 3: TodoWrite 初始化
设置业务分析师视角分析的任务跟踪：
```json
[
{"content": "Initialize business analyst brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze current business processes and workflows", "status": "in_progress", "activeForm": "Analyzing business processes"},
{"content": "Identify business requirements and stakeholder needs", "status": "pending", "activeForm": "Identifying requirements"},
{"content": "Evaluate cost-benefit and ROI analysis", "status": "pending", "activeForm": "Evaluating cost-benefit"},
{"content": "Design process improvements and optimizations", "status": "pending", "activeForm": "Designing improvements"},
{"content": "Plan change management and implementation", "status": "pending", "activeForm": "Planning change management"},
{"content": "Generate comprehensive business analysis documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct business analyst perspective brainstorming for: {topic}
ROLE CONTEXT: Business Analyst
- Focus Areas: Process optimization, requirements analysis, cost-benefit analysis, change management
- Analysis Framework: Business-centric approach with emphasis on efficiency and value creation
- Success Metrics: Process efficiency, cost reduction, stakeholder satisfaction, ROI achievement
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. Current State Business Analysis
- Map existing business processes and workflows
- Identify process inefficiencies and bottlenecks
- Analyze current costs, resources, and time investments
- Assess stakeholder roles and responsibilities
- Document pain points and improvement opportunities
2. Requirements Gathering and Analysis
- Identify key stakeholders and their needs
- Define functional and non-functional business requirements
- Prioritize requirements based on business value and urgency
- Analyze requirement dependencies and constraints
- Create requirements traceability matrix
3. Process Design and Optimization
- Design optimized future state processes
- Identify automation opportunities and digital solutions
- Plan for process standardization and best practices
- Design quality gates and control points
- Create process documentation and standard operating procedures
4. Cost-Benefit and ROI Analysis
- Calculate implementation costs (people, technology, time)
- Quantify expected benefits (cost savings, efficiency gains, revenue)
- Perform ROI analysis and payback period calculation
- Assess intangible benefits (customer satisfaction, employee morale)
- Create business case with financial justification
5. Risk Assessment and Mitigation
- Identify business, operational, and technical risks
- Assess impact and probability of identified risks
- Develop risk mitigation strategies and contingency plans
- Plan for compliance and regulatory requirements
- Design risk monitoring and control measures
6. Change Management and Implementation Planning
- Assess organizational change readiness and impact
- Design change management strategy and communication plan
- Plan training and knowledge transfer requirements
- Create implementation timeline with milestones
- Design success metrics and monitoring framework
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/business-analyst/
- analysis.md (main business analysis and process assessment)
- requirements.md (detailed business requirements and specifications)
- business-case.md (cost-benefit analysis and financial justification)
- implementation-plan.md (change management and implementation strategy)
Apply business analysis expertise to optimize processes and maximize business value."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/business-analyst/
├── analysis.md # 主要业务分析和流程评估
├── requirements.md # 详细业务需求和规范
├── business-case.md # 成本效益分析和财务论证
└── implementation-plan.md # 变更管理和实施策略
```
### 文档模板
#### analysis.md 结构
```markdown
# Business Analyst Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心业务分析发现和建议概述]
## Current State Assessment
### Business Process Mapping
### Stakeholder Analysis
### Performance Metrics Analysis
### Pain Points and Inefficiencies
## Business Requirements
### Functional Requirements
### Non-Functional Requirements
### Stakeholder Needs Analysis
### Requirements Prioritization
## Process Optimization Opportunities
### Automation Potential
### Workflow Improvements
### Resource Optimization
### Quality Enhancements
## Financial Analysis
### Cost-Benefit Analysis
### ROI Calculations
### Budget Requirements
### Financial Projections
## Risk Assessment
### Business Risks
### Operational Risks
### Mitigation Strategies
### Contingency Planning
## Implementation Strategy
### Change Management Plan
### Training Requirements
### Timeline and Milestones
### Success Metrics and KPIs
## Recommendations
### Immediate Actions (0-3 months)
### Medium-term Initiatives (3-12 months)
### Long-term Strategic Goals (12+ months)
### Resource Requirements
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"business_analyst": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/business-analyst/",
"key_insights": ["process_optimization", "cost_saving", "efficiency_gain"]
}
}
}
}
```
### 与其他角色的协作
业务分析师视角为其他角色提供：
- **业务需求和约束** → Product Manager
- **流程技术化需求** → System Architect
- **业务流程界面需求** → UI Designer
- **业务数据需求** → Data Architect
- **业务安全要求** → Security Expert
## ✅ **质量标准**
### 必须包含的分析元素
- [ ] 详细的业务流程映射
- [ ] 明确的需求规范和优先级
- [ ] 量化的成本效益分析
- [ ] 全面的风险评估
- [ ] 可执行的实施计划
### 业务分析原则检查
- [ ] 以价值为导向：关注商业价值创造
- [ ] 数据驱动：基于事实和数据进行分析
- [ ] 全局思维：考虑整个业务生态系统
- [ ] 风险意识：识别和管理各类风险
- [ ] 可持续性：长期可维护和改进
### 分析质量指标
- [ ] 需求的完整性和准确性
- [ ] 流程优化的量化收益
- [ ] 风险评估的全面性
- [ ] 实施计划的可行性
- [ ] 利益相关者的满意度

253
.claude/commands/workflow/brainstorm/data-architect.md Normal file
View File

@@ -0,0 +1,253 @@
---
name: brainstorm:data-architect
description: Data architect perspective brainstorming for data modeling, flow, and analytics analysis
usage: /brainstorm:data-architect <topic>
argument-hint: "topic or challenge to analyze from data architecture perspective"
examples:
- /brainstorm:data-architect "user analytics data pipeline"
- /brainstorm:data-architect "real-time data processing system"
- /brainstorm:data-architect "data warehouse modernization"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 📊 **角色定义: Data Architect**
### 核心职责
- **数据模型设计**: 设计高效、可扩展的数据模型
- **数据流程设计**: 规划数据采集、处理、存储流程
- **数据质量管理**: 确保数据准确性、完整性、一致性
- **分析和洞察**: 设计数据分析和商业智能解决方案
### 关注领域
- **数据建模**: 关系模型、NoSQL、数据仓库、湖仓一体
- **数据管道**: ETL/ELT流程、实时处理、批处理
- **数据治理**: 数据质量、安全、隐私、合规
- **分析平台**: BI工具、机器学习、报表系统
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **数据需求和来源**:
- 需要哪些数据来支持业务决策？
- 数据来源的可靠性和质量如何？
- 实时数据vs历史数据的需求平衡？
2. **数据架构和存储**:
- 最适合的数据存储方案是什么？
- 如何设计可扩展的数据模型？
- 数据分区和索引策略？
3. **数据处理和流程**:
- 数据处理的性能要求？
- 如何设计容错的数据管道？
- 数据变更和版本控制策略？
4. **分析和报告**:
- 如何支持不同的分析需求？
- 实时仪表板vs定期报告？
- 数据可视化和自助分析能力？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建数据架构师分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/data-architect/
```
### Phase 3: TodoWrite 初始化
设置数据架构师视角分析的任务跟踪：
```json
[
{"content": "Initialize data architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze data requirements and sources", "status": "in_progress", "activeForm": "Analyzing data requirements"},
{"content": "Design optimal data model and schema", "status": "pending", "activeForm": "Designing data model"},
{"content": "Plan data pipeline and processing workflows", "status": "pending", "activeForm": "Planning data pipelines"},
{"content": "Evaluate data quality and governance", "status": "pending", "activeForm": "Evaluating data governance"},
{"content": "Design analytics and reporting solutions", "status": "pending", "activeForm": "Designing analytics"},
{"content": "Generate comprehensive data architecture documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct data architect perspective brainstorming for: {topic}
ROLE CONTEXT: Data Architect
- Focus Areas: Data modeling, data flow, storage optimization, analytics infrastructure
- Analysis Framework: Data-driven approach with emphasis on scalability, quality, and insights
- Success Metrics: Data quality, processing efficiency, analytics accuracy, scalability
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. Data Requirements Analysis
- Identify all data sources (internal, external, third-party)
- Analyze data types, volumes, and velocity requirements
- Define data freshness and latency requirements
- Assess data quality and completeness standards
2. Data Architecture Design
- Design logical and physical data models
- Plan data storage strategy (relational, NoSQL, data lake, warehouse)
- Design data partitioning and sharding strategies
- Plan for data archival and retention policies
3. Data Pipeline and Processing
- Design ETL/ELT processes and data transformation workflows
- Plan real-time vs batch processing requirements
- Design error handling and data recovery mechanisms
- Plan for data lineage and audit trails
4. Data Quality and Governance
- Design data validation and quality monitoring
- Plan data governance framework and policies
- Assess privacy and compliance requirements (GDPR, CCPA, etc.)
- Design data access controls and security measures
5. Analytics and Reporting Infrastructure
- Design data warehouse/data mart architecture
- Plan business intelligence and reporting solutions
- Design self-service analytics capabilities
- Plan for machine learning and advanced analytics integration
6. Performance and Scalability
- Analyze current and projected data volumes
- Design indexing and query optimization strategies
- Plan horizontal and vertical scaling approaches
- Design monitoring and alerting for data systems
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/data-architect/
- analysis.md (main data architecture analysis)
- data-model.md (detailed data models and schemas)
- pipeline-design.md (data processing workflows and ETL design)
- governance-plan.md (data quality, security, and compliance framework)
Apply data architecture expertise to create scalable, reliable, and insightful data solutions."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/data-architect/
├── analysis.md # 主要数据架构分析
├── data-model.md # 详细数据模型和架构
├── pipeline-design.md # 数据处理工作流和ETL设计
└── governance-plan.md # 数据质量、安全和合规框架
```
### 文档模板
#### analysis.md 结构
```markdown
# Data Architect Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心数据架构发现和建议概述]
## Current Data Landscape Assessment
### Existing Data Sources
### Data Quality Issues
### Performance Bottlenecks
### Integration Challenges
## Data Requirements Analysis
### Business Data Requirements
### Technical Data Requirements
- Volume: [预期数据量和增长]
- Velocity: [数据更新频率]
- Variety: [数据类型和格式]
- Veracity: [数据质量要求]
## Proposed Data Architecture
### Data Storage Strategy
### Data Model Design
### Integration Architecture
### Analytics Infrastructure
## Data Pipeline Design
### Data Ingestion Strategy
### Processing Workflows
### Transformation Rules
### Quality Assurance
## Governance and Compliance
### Data Quality Framework
### Security and Privacy
### Audit and Lineage
### Compliance Requirements
## Performance and Scalability
### Optimization Strategies
### Scaling Plans
### Monitoring and Alerting
### Disaster Recovery
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"data_architect": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/data-architect/",
"key_insights": ["data_model_optimization", "pipeline_efficiency", "governance_requirement"]
}
}
}
}
```
### 与其他角色的协作
数据架构师视角为其他角色提供：
- **数据能力和限制** → Product Manager
- **数据存储要求** → System Architect
- **数据展示能力** → UI Designer
- **数据安全要求** → Security Expert
- **功能数据支持** → Feature Planner
## ✅ **质量标准**
### 必须包含的架构元素
- [ ] 完整的数据模型设计
- [ ] 详细的数据流程图
- [ ] 数据质量保证方案
- [ ] 可扩展性和性能优化
- [ ] 合规和安全控制
### 数据架构原则检查
- [ ] 可扩展性：支持数据量和用户增长
- [ ] 可靠性：具有容错和恢复机制
- [ ] 可维护性：清晰的数据模型和流程
- [ ] 安全性：数据保护和访问控制
- [ ] 高效性：优化的查询和处理性能
### 数据质量指标
- [ ] 数据准确性和完整性标准
- [ ] 数据一致性检查机制
- [ ] 数据时效性和新鲜度要求
- [ ] 数据可追溯性和审计能力
- [ ] 合规性检查和报告机制

263
.claude/commands/workflow/brainstorm/feature-planner.md Normal file
View File

@@ -0,0 +1,263 @@
---
name: brainstorm:feature-planner
description: Feature planner perspective brainstorming for feature development and planning analysis
usage: /brainstorm:feature-planner <topic>
argument-hint: "topic or challenge to analyze from feature planning perspective"
examples:
- /brainstorm:feature-planner "user dashboard enhancement"
- /brainstorm:feature-planner "mobile app feature roadmap"
- /brainstorm:feature-planner "integration capabilities planning"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🔧 **角色定义: Feature Planner**
### 核心职责
- **功能规划**: 设计和规划产品功能的开发路线图
- **需求转化**: 将业务需求转化为具体的功能规范
- **优先级排序**: 基于价值和资源平衡功能开发优先级
- **交付规划**: 制定功能开发和发布时间表
### 关注领域
- **功能设计**: 功能规范、用户故事、验收标准
- **开发规划**: 迭代计划、里程碑、依赖关系管理
- **质量保证**: 测试策略、质量标准、验收流程
- **发布管理**: 发布策略、版本控制、变更管理
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **功能需求分析**:
- 核心功能需求和用户故事？
- 功能的MVP和完整版本规划？
- 跨功能依赖和集成需求？
2. **技术可行性评估**:
- 技术实现的复杂度和挑战？
- 现有系统的扩展和改造需求？
- 第三方服务和API集成？
3. **开发资源和时间估算**:
- 开发工作量和时间预估？
- 所需技能和团队配置？
- 开发风险和缓解策略？
4. **测试和质量保证**:
- 测试策略和测试用例设计？
- 质量标准和验收条件？
- 用户验收和反馈机制？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建功能规划师分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/feature-planner/
```
### Phase 3: TodoWrite 初始化
设置功能规划师视角分析的任务跟踪：
```json
[
{"content": "Initialize feature planner brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze feature requirements and user stories", "status": "in_progress", "activeForm": "Analyzing feature requirements"},
{"content": "Design feature architecture and specifications", "status": "pending", "activeForm": "Designing feature architecture"},
{"content": "Plan development phases and prioritization", "status": "pending", "activeForm": "Planning development phases"},
{"content": "Evaluate testing strategy and quality assurance", "status": "pending", "activeForm": "Evaluating testing strategy"},
{"content": "Create implementation timeline and milestones", "status": "pending", "activeForm": "Creating timeline"},
{"content": "Generate comprehensive feature planning documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct feature planner perspective brainstorming for: {topic}
ROLE CONTEXT: Feature Planner
- Focus Areas: Feature specification, development planning, quality assurance, delivery management
- Analysis Framework: Feature-centric approach with emphasis on deliverability and user value
- Success Metrics: Feature completion, quality standards, user satisfaction, delivery timeline
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. Feature Requirements Analysis
- Break down high-level requirements into specific feature specifications
- Create detailed user stories with acceptance criteria
- Identify feature dependencies and integration requirements
- Map features to user personas and use cases
- Define feature scope and boundaries (MVP vs full feature)
2. Feature Architecture and Design
- Design feature workflows and user interaction patterns
- Plan feature integration with existing system components
- Define APIs and data interfaces required
- Plan for feature configuration and customization options
- Design feature monitoring and analytics capabilities
3. Development Planning and Estimation
- Estimate development effort and complexity for each feature
- Identify technical risks and implementation challenges
- Plan feature development phases and incremental delivery
- Define development milestones and checkpoints
- Assess resource requirements and team capacity
4. Quality Assurance and Testing Strategy
- Design comprehensive testing strategy (unit, integration, E2E)
- Create test scenarios and edge case coverage
- Plan performance testing and scalability validation
- Design user acceptance testing procedures
- Plan for accessibility and usability testing
5. Feature Prioritization and Roadmap
- Apply prioritization frameworks (MoSCoW, Kano, RICE)
- Balance business value with development complexity
- Create feature release planning and versioning strategy
- Plan for feature flags and gradual rollout
- Design feature deprecation and sunset strategies
6. Delivery and Release Management
- Plan feature delivery timeline and release schedule
- Design change management and deployment strategies
- Plan for feature documentation and user training
- Create feature success metrics and KPIs
- Design post-release monitoring and support plans
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/feature-planner/
- analysis.md (main feature analysis and specifications)
- user-stories.md (detailed user stories and acceptance criteria)
- development-plan.md (development timeline and resource planning)
- testing-strategy.md (quality assurance and testing approach)
Apply feature planning expertise to create deliverable, high-quality feature implementations."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/feature-planner/
├── analysis.md # 主要功能分析和规范
├── user-stories.md # 详细用户故事和验收标准
├── development-plan.md # 开发时间线和资源规划
└── testing-strategy.md # 质量保证和测试方法
```
### 文档模板
#### analysis.md 结构
```markdown
# Feature Planner Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心功能规划发现和建议概述]
## Feature Requirements Overview
### Core Feature Specifications
### User Story Summary
### Feature Scope and Boundaries
### Success Criteria and KPIs
## Feature Architecture Design
### Feature Components and Modules
### Integration Points and Dependencies
### APIs and Data Interfaces
### Configuration and Customization
## Development Planning
### Effort Estimation and Complexity
### Development Phases and Milestones
### Resource Requirements
### Risk Assessment and Mitigation
## Quality Assurance Strategy
### Testing Approach and Coverage
### Performance and Scalability Testing
### User Acceptance Testing Plan
### Quality Gates and Standards
## Delivery and Release Strategy
### Release Planning and Versioning
### Deployment Strategy
### Feature Rollout Plan
### Post-Release Support
## Feature Prioritization
### Priority Matrix (High/Medium/Low)
### Business Value Assessment
### Development Complexity Analysis
### Recommended Implementation Order
## Implementation Roadmap
### Phase 1: Core Features (Weeks 1-4)
### Phase 2: Enhanced Features (Weeks 5-8)
### Phase 3: Advanced Features (Weeks 9-12)
### Continuous Improvement Plan
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"feature_planner": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/feature-planner/",
"key_insights": ["feature_specification", "development_timeline", "quality_requirement"]
}
}
}
}
```
### 与其他角色的协作
功能规划师视角为其他角色提供：
- **功能优先级和规划** → Product Manager
- **技术实现需求** → System Architect
- **界面功能要求** → UI Designer
- **数据功能需求** → Data Architect
- **功能安全需求** → Security Expert
## ✅ **质量标准**
### 必须包含的规划元素
- [ ] 详细的功能规范和用户故事
- [ ] 现实的开发时间估算
- [ ] 全面的测试策略
- [ ] 明确的质量标准
- [ ] 可执行的发布计划
### 功能规划原则检查
- [ ] 用户价值：每个功能都有明确的用户价值
- [ ] 可测试性：所有功能都有验收标准
- [ ] 可维护性：考虑长期维护和扩展
- [ ] 可交付性：计划符合团队能力和资源
- [ ] 可测量性：有明确的成功指标
### 交付质量评估
- [ ] 功能完整性和正确性
- [ ] 性能和稳定性指标
- [ ] 用户体验和满意度
- [ ] 代码质量和可维护性
- [ ] 文档完整性和准确性

263
.claude/commands/workflow/brainstorm/innovation-lead.md Normal file
View File

@@ -0,0 +1,263 @@
---
name: brainstorm:innovation-lead
description: Innovation lead perspective brainstorming for emerging technologies and future opportunities analysis
usage: /brainstorm:innovation-lead <topic>
argument-hint: "topic or challenge to analyze from innovation and emerging technology perspective"
examples:
- /brainstorm:innovation-lead "AI integration opportunities"
- /brainstorm:innovation-lead "future technology trends"
- /brainstorm:innovation-lead "disruptive innovation strategy"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🚀 **角色定义: Innovation Lead**
### 核心职责
- **趋势识别**: 识别和分析新兴技术趋势和市场机会
- **创新策略**: 制定创新路线图和技术发展战略
- **技术评估**: 评估新技术的应用潜力和可行性
- **未来规划**: 设计面向未来的产品和服务概念
### 关注领域
- **新兴技术**: AI、区块链、IoT、AR/VR、量子计算等前沿技术
- **市场趋势**: 行业变革、用户行为演进、商业模式创新
- **创新机会**: 破坏性创新、蓝海市场、技术融合机会
- **未来愿景**: 长期技术路线图、概念验证、原型开发
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **技术趋势和机会**:
- 哪些新兴技术对我们的行业最有影响？
- 技术成熟度和采用时间轴？
- 技术融合创造的新机会？
2. **创新潜力评估**:
- 破坏性创新的可能性和影响？
- 现有解决方案的创新空间？
- 未被满足的市场需求？
3. **竞争和市场分析**:
- 竞争对手的创新动向？
- 市场空白和蓝海机会？
- 技术壁垒和先发优势？
4. **实施和风险评估**:
- 技术实施的可行性和风险？
- 投资需求和预期回报？
- 组织创新能力和适应性？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建创新领导分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/innovation-lead/
```
### Phase 3: TodoWrite 初始化
设置创新领导视角分析的任务跟踪：
```json
[
{"content": "Initialize innovation lead brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Research emerging technology trends and opportunities", "status": "in_progress", "activeForm": "Researching technology trends"},
{"content": "Analyze innovation potential and market disruption", "status": "pending", "activeForm": "Analyzing innovation potential"},
{"content": "Evaluate competitive landscape and positioning", "status": "pending", "activeForm": "Evaluating competitive landscape"},
{"content": "Design future-oriented solutions and concepts", "status": "pending", "activeForm": "Designing future solutions"},
{"content": "Assess implementation feasibility and roadmap", "status": "pending", "activeForm": "Assessing implementation"},
{"content": "Generate comprehensive innovation strategy documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct innovation lead perspective brainstorming for: {topic}
ROLE CONTEXT: Innovation Lead
- Focus Areas: Emerging technologies, market disruption, future opportunities, innovation strategy
- Analysis Framework: Forward-thinking approach with emphasis on breakthrough innovation and competitive advantage
- Success Metrics: Innovation impact, market differentiation, technology adoption, future readiness
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. Emerging Technology Landscape Analysis
- Research current and emerging technology trends relevant to the topic
- Analyze technology maturity levels and adoption curves
- Identify breakthrough technologies with disruptive potential
- Assess technology convergence opportunities and synergies
- Map technology evolution timelines and critical milestones
2. Innovation Opportunity Assessment
- Identify unmet market needs and whitespace opportunities
- Analyze potential for disruptive innovation vs incremental improvement
- Assess blue ocean market opportunities and new value propositions
- Evaluate cross-industry innovation transfer possibilities
- Identify platform and ecosystem innovation opportunities
3. Competitive Intelligence and Market Analysis
- Analyze competitor innovation strategies and technology investments
- Identify market leaders and emerging disruptors
- Assess patent landscapes and intellectual property opportunities
- Evaluate startup ecosystem and potential acquisition targets
- Analyze venture capital and funding trends in related areas
4. Future Scenario Planning
- Design multiple future scenarios based on technology trends
- Create technology roadmaps with short, medium, and long-term horizons
- Identify potential black swan events and wild card scenarios
- Plan for technology convergence and platform shifts
- Design adaptive strategies for uncertain futures
5. Innovation Concept Development
- Generate breakthrough product and service concepts
- Design minimum viable innovation experiments
- Create proof-of-concept prototyping strategies
- Plan innovation pilot programs and validation approaches
- Design scalable innovation frameworks and processes
6. Implementation Strategy and Risk Assessment
- Assess organizational innovation readiness and capabilities
- Identify required technology investments and partnerships
- Evaluate risks including technology, market, and execution risks
- Design innovation governance and decision-making frameworks
- Plan talent acquisition and capability building strategies
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/innovation-lead/
- analysis.md (main innovation analysis and opportunity assessment)
- technology-roadmap.md (technology trends and future scenarios)
- innovation-concepts.md (breakthrough ideas and concept development)
- strategy-implementation.md (innovation strategy and execution plan)
Apply innovation leadership expertise to identify breakthrough opportunities and design future-ready strategies."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/innovation-lead/
├── analysis.md # 主要创新分析和机会评估
├── technology-roadmap.md # 技术趋势和未来场景
├── innovation-concepts.md # 突破性想法和概念开发
└── strategy-implementation.md # 创新策略和执行计划
```
### 文档模板
#### analysis.md 结构
```markdown
# Innovation Lead Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心创新机会和战略建议概述]
## Technology Landscape Assessment
### Emerging Technologies Overview
### Technology Maturity Analysis
### Convergence Opportunities
### Disruptive Potential Assessment
## Innovation Opportunity Analysis
### Market Whitespace Identification
### Unmet Needs and Pain Points
### Disruptive Innovation Potential
### Blue Ocean Opportunities
## Competitive Intelligence
### Competitor Innovation Strategies
### Patent Landscape Analysis
### Startup Ecosystem Insights
### Investment and Funding Trends
## Future Scenarios and Trends
### Short-term Innovations (0-2 years)
### Medium-term Disruptions (2-5 years)
### Long-term Transformations (5+ years)
### Wild Card Scenarios
## Innovation Concepts
### Breakthrough Ideas
### Proof-of-Concept Opportunities
### Platform Innovation Possibilities
### Ecosystem Partnership Ideas
## Strategic Recommendations
### Innovation Investment Priorities
### Technology Partnership Strategy
### Capability Building Requirements
### Risk Mitigation Approaches
## Implementation Roadmap
### Innovation Pilot Programs
### Technology Validation Milestones
### Scaling and Commercialization Plan
### Success Metrics and KPIs
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"innovation_lead": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/innovation-lead/",
"key_insights": ["breakthrough_opportunity", "emerging_technology", "disruptive_potential"]
}
}
}
}
```
### 与其他角色的协作
创新领导视角为其他角色提供：
- **创新机会和趋势** → Product Manager
- **新技术可行性** → System Architect
- **未来用户体验趋势** → UI Designer
- **新兴数据技术** → Data Architect
- **创新安全挑战** → Security Expert
## ✅ **质量标准**
### 必须包含的创新元素
- [ ] 全面的技术趋势分析
- [ ] 明确的创新机会识别
- [ ] 具体的概念验证方案
- [ ] 现实的实施路线图
- [ ] 前瞻性的风险评估
### 创新思维原则检查
- [ ] 前瞻性：关注未来3-10年趋势
- [ ] 颠覆性：寻找破坏性创新机会
- [ ] 系统性：考虑技术生态系统影响
- [ ] 可行性：平衡愿景与现实可能
- [ ] 差异化：创造独特竞争优势
### 创新价值评估
- [ ] 市场影响的潜在规模
- [ ] 技术可行性和成熟度
- [ ] 竞争优势的可持续性
- [ ] 投资回报的时间框架
- [ ] 组织实施的复杂度

217
.claude/commands/workflow/brainstorm/product-manager.md Normal file
View File

@@ -0,0 +1,217 @@
---
name: brainstorm:product-manager
description: Product manager perspective brainstorming for user needs and business value analysis
usage: /brainstorm:product-manager <topic>
argument-hint: "topic or challenge to analyze from product management perspective"
examples:
- /brainstorm:product-manager "user authentication redesign"
- /brainstorm:product-manager "mobile app performance optimization"
- /brainstorm:product-manager "feature prioritization strategy"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🎯 **角色定义: Product Manager**
### 核心职责
- **用户需求分析**: 深度理解用户痛点和需求
- **商业价值评估**: 评估功能和改进的商业影响
- **市场定位**: 分析竞争环境和市场机会
- **产品战略**: 制定产品路线图和优先级
### 关注领域
- **用户体验**: 用户旅程、满意度、转化率
- **商业指标**: ROI、用户增长、留存率、收入影响
- **市场竞争**: 竞品分析、差异化优势、市场趋势
- **产品生命周期**: 功能演进、技术债务、可维护性
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **用户价值**:
- 这个功能/改进解决了什么真实问题？
- 目标用户群体是谁？他们的核心需求是什么？
- 用户愿意为此付费/投入时间吗？
2. **商业影响**:
- 预期的商业收益是什么？
- 实施成本vs预期回报如何？
- 对现有业务流程有何影响？
3. **市场机会**:
- 市场上现有解决方案的不足在哪？
- 我们的差异化优势是什么？
- 时机是否合适？
4. **执行可行性**:
- 所需资源和时间估算？
- 技术可行性和风险评估？
- 团队能力匹配度？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建产品经理分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/product-manager/
```
### Phase 3: TodoWrite 初始化
设置产品经理视角分析的任务跟踪：
```json
[
{"content": "Initialize product manager brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze user needs and pain points", "status": "in_progress", "activeForm": "Analyzing user needs"},
{"content": "Evaluate business value and impact", "status": "pending", "activeForm": "Evaluating business impact"},
{"content": "Assess market opportunities", "status": "pending", "activeForm": "Assessing market opportunities"},
{"content": "Develop product strategy recommendations", "status": "pending", "activeForm": "Developing strategy"},
{"content": "Create prioritized action plan", "status": "pending", "activeForm": "Creating action plan"},
{"content": "Generate comprehensive product analysis", "status": "pending", "activeForm": "Generating analysis"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct product management perspective brainstorming for: {topic}
ROLE CONTEXT: Product Manager
- Focus Areas: User needs, business value, market positioning, product strategy
- Analysis Framework: User-centric approach with business impact assessment
- Success Metrics: User satisfaction, business growth, market differentiation
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. User Needs Analysis
- Identify core user problems and pain points
- Define target user segments and personas
- Map user journey and experience gaps
- Prioritize user requirements by impact and frequency
2. Business Value Assessment
- Quantify potential business impact (revenue, growth, efficiency)
- Analyze cost-benefit ratio and ROI projections
- Identify key success metrics and KPIs
- Assess risk factors and mitigation strategies
3. Market Opportunity Analysis
- Competitive landscape and gap analysis
- Market trends and emerging opportunities
- Differentiation strategies and unique value propositions
- Go-to-market considerations
4. Product Strategy Development
- Feature prioritization matrix
- Product roadmap recommendations
- Resource allocation strategies
- Implementation timeline and milestones
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/product-manager/
- analysis.md (main product management analysis)
- business-case.md (business justification and metrics)
- user-research.md (user needs and market insights)
- roadmap.md (strategic recommendations and timeline)
Apply product management expertise to generate actionable insights addressing business goals and user needs."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/product-manager/
├── analysis.md # 主要产品分析
├── business-case.md # 商业论证和指标
├── user-research.md # 用户研究和市场洞察
└── roadmap.md # 战略建议和时间线
```
### 文档模板
#### analysis.md 结构
```markdown
# Product Manager Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心发现和建议概述]
## User Needs Analysis
### Target User Segments
### Core Problems Identified
### User Journey Mapping
### Priority Requirements
## Business Impact Assessment
### Revenue Impact
### Cost Analysis
### ROI Projections
### Risk Assessment
## Competitive Analysis
### Market Position
### Differentiation Opportunities
### Competitive Advantages
## Strategic Recommendations
### Immediate Actions (0-3 months)
### Medium-term Initiatives (3-12 months)
### Long-term Vision (12+ months)
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"product_manager": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/product-manager/",
"key_insights": ["insight1", "insight2", "insight3"]
}
}
}
}
```
### 与其他角色的协作
产品经理视角为其他角色提供：
- **用户需求定义** → UI Designer
- **业务约束和目标** → System Architect
- **功能优先级** → Feature Planner
- **市场要求** → Innovation Lead
## ✅ **质量标准**
### 必须包含的分析元素
- [ ] 明确的用户价值主张
- [ ] 量化的业务影响评估
- [ ] 可执行的产品策略建议
- [ ] 基于数据的优先级排序
- [ ] 清晰的成功指标定义
### 输出质量检查
- [ ] 分析基于真实用户需求
- [ ] 商业论证逻辑清晰
- [ ] 建议具有可操作性
- [ ] 时间线合理可行
- [ ] 风险识别全面准确

261
.claude/commands/workflow/brainstorm/security-expert.md Normal file
View File

@@ -0,0 +1,261 @@
---
name: brainstorm:security-expert
description: Security expert perspective brainstorming for threat modeling and security architecture analysis
usage: /brainstorm:security-expert <topic>
argument-hint: "topic or challenge to analyze from security perspective"
examples:
- /brainstorm:security-expert "user authentication security"
- /brainstorm:security-expert "API security architecture"
- /brainstorm:security-expert "data privacy compliance"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🔒 **角色定义: Security Expert**
### 核心职责
- **威胁建模**: 识别和评估安全威胁和攻击向量
- **安全架构**: 设计防御性安全控制和保护机制
- **合规评估**: 确保符合安全标准和法规要求
- **风险管理**: 评估和缓解安全风险
### 关注领域
- **应用安全**: 代码安全、输入验证、会话管理
- **基础设施安全**: 网络安全、服务器加固、云安全
- **数据保护**: 数据加密、访问控制、隐私保护
- **合规管理**: GDPR、SOC2、ISO27001、行业标准
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **威胁识别和建模**:
- 主要的安全威胁和攻击向量是什么？
- 资产价值和风险评估？
- 攻击者画像和攻击路径分析？
2. **安全控制和防护**:
- 需要实施哪些安全控制？
- 身份认证和授权机制？
- 数据保护和加密策略？
3. **合规和标准**:
- 适用的合规要求和标准？
- 安全审计和监控需求？
- 事件响应和恢复计划？
4. **风险评估和缓解**:
- 安全风险等级和影响评估？
- 风险缓解策略和优先级？
- 持续监控和改进机制？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建安全专家分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/security-expert/
```
### Phase 3: TodoWrite 初始化
设置安全专家视角分析的任务跟踪：
```json
[
{"content": "Initialize security expert brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Conduct threat modeling and risk assessment", "status": "in_progress", "activeForm": "Conducting threat modeling"},
{"content": "Design security architecture and controls", "status": "pending", "activeForm": "Designing security architecture"},
{"content": "Evaluate compliance requirements", "status": "pending", "activeForm": "Evaluating compliance"},
{"content": "Plan incident response and monitoring", "status": "pending", "activeForm": "Planning incident response"},
{"content": "Assess data protection and privacy", "status": "pending", "activeForm": "Assessing data protection"},
{"content": "Generate comprehensive security documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct security expert perspective brainstorming for: {topic}
ROLE CONTEXT: Security Expert
- Focus Areas: Threat modeling, security architecture, compliance, risk management
- Analysis Framework: Defense-in-depth approach with risk-based security controls
- Success Metrics: Threat coverage, vulnerability reduction, compliance adherence, incident response time
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. Threat Modeling and Risk Assessment
- Identify threat actors and attack vectors
- Analyze attack surfaces and entry points
- Assess asset value and potential impact
- Create threat model diagrams and scenarios
- Evaluate existing security posture and gaps
2. Security Architecture Design
- Design authentication and authorization mechanisms
- Plan encryption strategies for data at rest and in transit
- Design network security and segmentation
- Plan secure communication protocols and APIs
- Design security monitoring and logging architecture
3. Application Security Assessment
- Analyze input validation and sanitization requirements
- Assess session management and CSRF protection
- Evaluate SQL injection and XSS vulnerabilities
- Plan secure coding practices and code review processes
- Design security testing and penetration testing strategies
4. Compliance and Regulatory Requirements
- Assess applicable regulations (GDPR, CCPA, HIPAA, PCI-DSS, etc.)
- Map compliance requirements to security controls
- Plan audit trails and documentation requirements
- Design privacy impact assessments
- Plan compliance monitoring and reporting
5. Incident Response and Recovery
- Design security incident detection and alerting
- Plan incident response procedures and escalation
- Design forensic analysis and evidence collection
- Plan business continuity and disaster recovery
- Design security awareness and training programs
6. Data Protection and Privacy
- Design data classification and handling procedures
- Plan data retention and disposal strategies
- Assess third-party data sharing risks
- Design privacy controls and user consent management
- Plan data breach notification procedures
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/security-expert/
- analysis.md (main security analysis and threat model)
- security-architecture.md (detailed security controls and architecture)
- compliance-framework.md (regulatory requirements and compliance plan)
- incident-response.md (security incident management and recovery procedures)
Apply security expertise to create robust, compliant, and resilient security solutions."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/security-expert/
├── analysis.md # 主要安全分析和威胁建模
├── security-architecture.md # 详细安全控制和架构
├── compliance-framework.md # 法规要求和合规计划
└── incident-response.md # 安全事件管理和恢复程序
```
### 文档模板
#### analysis.md 结构
```markdown
# Security Expert Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心安全发现和建议概述]
## Threat Modeling
### Threat Actors
- Internal threats: [内部威胁分析]
- External threats: [外部威胁分析]
- Threat capabilities and motivations
### Attack Vectors
### Attack Surface Analysis
### Risk Assessment Matrix
## Current Security Posture
### Existing Security Controls
### Identified Vulnerabilities
### Security Gaps and Weaknesses
### Compliance Status
## Security Architecture Recommendations
### Authentication and Authorization
### Data Protection Strategy
### Network Security Design
### Application Security Controls
## Risk Management
### Critical Risks Identified
### Risk Mitigation Strategies
### Security Control Prioritization
### Residual Risk Assessment
## Compliance Requirements
### Applicable Regulations
### Compliance Gaps
### Required Documentation
### Audit Preparation
## Implementation Roadmap
### Immediate Security Actions (0-30 days)
### Short-term Improvements (1-6 months)
### Long-term Security Strategy (6+ months)
### Success Metrics and KPIs
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"security_expert": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/security-expert/",
"key_insights": ["critical_vulnerability", "compliance_requirement", "security_control"]
}
}
}
}
```
### 与其他角色的协作
安全专家视角为其他角色提供：
- **安全要求和约束** → System Architect
- **安全合规影响** → Product Manager
- **安全用户体验** → UI Designer
- **数据安全要求** → Data Architect
- **安全功能需求** → Feature Planner
## ✅ **质量标准**
### 必须包含的安全元素
- [ ] 全面的威胁模型和风险评估
- [ ] 详细的安全架构和控制设计
- [ ] 合规要求映射和实施计划
- [ ] 事件响应和恢复程序
- [ ] 安全监控和测试策略
### 安全框架检查
- [ ] 防御深度：多层安全控制
- [ ] 最小权限：访问控制最小化
- [ ] 失败安全：安全失败时的默认行为
- [ ] 完整监控：全面的安全日志和告警
- [ ] 持续改进：定期安全评估和更新
### 威胁覆盖验证
- [ ] OWASP Top 10 威胁评估
- [ ] 内部和外部威胁分析
- [ ] 供应链安全风险
- [ ] 云安全和配置管理
- [ ] 隐私和数据保护合规

299
.claude/commands/workflow/brainstorm/synthesis.md Normal file
View File

@@ -0,0 +1,299 @@
---
name: brainstorm:synthesis
description: Synthesize all brainstorming role perspectives into comprehensive analysis and recommendations
usage: /brainstorm:synthesis
argument-hint: "no arguments required - analyzes existing brainstorming session outputs"
examples:
- /brainstorm:synthesis
allowed-tools: Read(*), Write(*), TodoWrite(*), Glob(*)
---
## 🧩 **命令定义: Brainstorm Synthesis**
### 核心功能
- **跨角色综合**: 整合所有角色的头脑风暴分析结果
- **洞察提炼**: 识别共识点、分歧点和创新机会
- **决策支持**: 生成优先级建议和行动计划
- **报告生成**: 创建综合性的头脑风暴总结报告
### 分析范围
- **产品管理**: 用户需求、商业价值、市场机会
- **技术架构**: 系统设计、技术选型、实施可行性
- **用户体验**: 界面设计、可用性、可访问性
- **数据架构**: 数据模型、处理流程、分析能力
- **安全专家**: 威胁评估、安全控制、合规要求
- **用户研究**: 行为洞察、需求验证、体验优化
- **业务分析**: 流程优化、成本效益、变更管理
- **创新领导**: 技术趋势、创新机会、未来规划
- **功能规划**: 开发计划、质量保证、交付管理
## ⚙️ **执行协议**
### Phase 1: 会话检测与数据收集
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
ERROR: "No active brainstorming session found. Please run role-specific brainstorming commands first."
EXIT
```
### Phase 2: 角色输出扫描
```bash
# 扫描所有角色的头脑风暴输出
SCAN_DIRECTORY: .workflow/WFS-{session}/.brainstorming/
COLLECT_OUTPUTS: [
product-manager/analysis.md,
system-architect/analysis.md,
ui-designer/analysis.md,
data-architect/analysis.md,
security-expert/analysis.md,
user-researcher/analysis.md,
business-analyst/analysis.md,
innovation-lead/analysis.md,
feature-planner/analysis.md
]
```
### Phase 3: TodoWrite 初始化
设置综合分析任务跟踪：
```json
[
{"content": "Initialize synthesis brainstorming session", "status": "completed", "activeForm": "Initializing synthesis"},
{"content": "Collect and analyze all role perspectives", "status": "in_progress", "activeForm": "Collecting role analyses"},
{"content": "Identify cross-role insights and patterns", "status": "pending", "activeForm": "Identifying insights"},
{"content": "Generate consensus and disagreement analysis", "status": "pending", "activeForm": "Analyzing consensus"},
{"content": "Create prioritized recommendations matrix", "status": "pending", "activeForm": "Creating recommendations"},
{"content": "Generate comprehensive synthesis report", "status": "pending", "activeForm": "Generating synthesis report"},
{"content": "Create action plan with implementation priorities", "status": "pending", "activeForm": "Creating action plan"}
]
```
### Phase 4: 综合分析执行
#### 4.1 数据收集和预处理
```pseudo
FOR each role_directory in brainstorming_roles:
IF role_directory exists:
role_analysis = Read(role_directory + "/analysis.md")
role_recommendations = Read(role_directory + "/recommendations.md") IF EXISTS
role_insights[role] = extract_key_insights(role_analysis)
role_recommendations[role] = extract_recommendations(role_analysis)
role_concerns[role] = extract_concerns_risks(role_analysis)
END IF
END FOR
```
#### 4.2 跨角色洞察分析
```pseudo
# 共识点识别
consensus_areas = identify_common_themes(role_insights)
agreement_matrix = create_agreement_matrix(role_recommendations)
# 分歧点分析
disagreement_areas = identify_conflicting_views(role_insights)
tension_points = analyze_role_conflicts(role_recommendations)
# 创新机会提取
innovation_opportunities = extract_breakthrough_ideas(role_insights)
synergy_opportunities = identify_cross_role_synergies(role_insights)
```
#### 4.3 优先级和决策矩阵生成
```pseudo
# 创建综合评估矩阵
FOR each recommendation:
impact_score = calculate_business_impact(recommendation, role_insights)
feasibility_score = calculate_technical_feasibility(recommendation, role_insights)
effort_score = calculate_implementation_effort(recommendation, role_insights)
risk_score = calculate_associated_risks(recommendation, role_insights)
priority_score = weighted_score(impact_score, feasibility_score, effort_score, risk_score)
END FOR
SORT recommendations BY priority_score DESC
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/
├── synthesis-report.md # 综合分析报告
├── recommendations-matrix.md # 优先级推荐矩阵
├── action-plan.md # 实施行动计划
├── consensus-analysis.md # 共识和分歧分析
└── brainstorm-summary.json # 机器可读的综合数据
```
### 核心输出文档
#### synthesis-report.md 结构
```markdown
# Brainstorming Synthesis Report: {Topic}
*Generated: {timestamp} | Session: WFS-{topic-slug}*
## Executive Summary
### Key Findings Overview
### Strategic Recommendations
### Implementation Priority
### Success Metrics
## Participating Perspectives Analysis
### Roles Analyzed: {list_of_completed_roles}
### Coverage Assessment: {completeness_percentage}%
### Analysis Quality Score: {quality_assessment}
## Cross-Role Insights Synthesis
### 🤝 Consensus Areas
**Strong Agreement (3+ roles)**:
1. **{consensus_theme_1}**
- Supporting roles: {role1, role2, role3}
- Key insight: {shared_understanding}
- Business impact: {impact_assessment}
2. **{consensus_theme_2}**
- Supporting roles: {role1, role2, role4}
- Key insight: {shared_understanding}
- Business impact: {impact_assessment}
### ⚡ Breakthrough Ideas
**Innovation Opportunities**:
1. **{breakthrough_idea_1}**
- Origin: {source_role}
- Cross-role support: {supporting_roles}
- Innovation potential: {potential_assessment}
2. **{breakthrough_idea_2}**
- Origin: {source_role}
- Cross-role support: {supporting_roles}
- Innovation potential: {potential_assessment}
### 🔄 Areas of Disagreement
**Tension Points Requiring Resolution**:
1. **{disagreement_area_1}**
- Conflicting views: {role1_view} vs {role2_view}
- Root cause: {underlying_issue}
- Resolution approach: {recommended_resolution}
2. **{disagreement_area_2}**
- Conflicting views: {role1_view} vs {role2_view}
- Root cause: {underlying_issue}
- Resolution approach: {recommended_resolution}
## Comprehensive Recommendations Matrix
### 🎯 High Priority (Immediate Action)
| Recommendation | Business Impact | Technical Feasibility | Implementation Effort | Risk Level | Supporting Roles |
|----------------|-----------------|----------------------|---------------------|------------|------------------|
| {rec_1} | High | High | Medium | Low | PM, Arch, UX |
| {rec_2} | High | Medium | Low | Medium | BA, PM, FP |
### 📋 Medium Priority (Strategic Planning)
| Recommendation | Business Impact | Technical Feasibility | Implementation Effort | Risk Level | Supporting Roles |
|----------------|-----------------|----------------------|---------------------|------------|------------------|
| {rec_3} | Medium | High | High | Medium | Arch, DA, Sec |
| {rec_4} | Medium | Medium | Medium | Low | UX, UR, PM |
### 🔬 Research Priority (Future Investigation)
| Recommendation | Business Impact | Technical Feasibility | Implementation Effort | Risk Level | Supporting Roles |
|----------------|-----------------|----------------------|---------------------|------------|------------------|
| {rec_5} | High | Unknown | High | High | IL, Arch, PM |
| {rec_6} | Medium | Low | High | High | IL, DA, Sec |
## Implementation Strategy
### Phase 1: Foundation (0-3 months)
- **Focus**: High-priority, low-effort recommendations
- **Key Actions**: {action_list}
- **Success Metrics**: {metrics_list}
- **Required Resources**: {resource_list}
### Phase 2: Development (3-9 months)
- **Focus**: Medium-priority strategic initiatives
- **Key Actions**: {action_list}
- **Success Metrics**: {metrics_list}
- **Required Resources**: {resource_list}
### Phase 3: Innovation (9+ months)
- **Focus**: Research and breakthrough opportunities
- **Key Actions**: {action_list}
- **Success Metrics**: {metrics_list}
- **Required Resources**: {resource_list}
## Risk Assessment and Mitigation
### Critical Risks Identified
1. **{risk_1}**: {description} | Mitigation: {strategy}
2. **{risk_2}**: {description} | Mitigation: {strategy}
### Success Factors
- {success_factor_1}
- {success_factor_2}
- {success_factor_3}
## Next Steps and Follow-up
### Immediate Actions Required
### Decision Points Needing Resolution
### Continuous Monitoring Requirements
### Future Brainstorming Sessions Recommended
---
*This synthesis integrates insights from {role_count} perspectives to provide comprehensive strategic guidance.*
```
## 🔄 **会话集成**
### 状态同步
综合分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"status": "completed",
"synthesis_completed": true,
"completed_at": "timestamp",
"participating_roles": ["product-manager", "system-architect", "ui-designer", ...],
"key_outputs": {
"synthesis_report": ".workflow/WFS-{topic}/.brainstorming/synthesis-report.md",
"action_plan": ".workflow/WFS-{topic}/.brainstorming/action-plan.md",
"recommendations_matrix": ".workflow/WFS-{topic}/.brainstorming/recommendations-matrix.md"
},
"metrics": {
"roles_analyzed": 9,
"consensus_areas": 5,
"breakthrough_ideas": 3,
"high_priority_recommendations": 8,
"implementation_phases": 3
}
}
}
}
```
## ✅ **质量标准**
### 必须包含的综合元素
- [ ] 所有可用角色分析的整合
- [ ] 明确的共识和分歧识别
- [ ] 量化的优先级推荐矩阵
- [ ] 可执行的实施计划
- [ ] 全面的风险评估和缓解
### 综合分析质量检查
- [ ] **完整性**: 整合所有可用的角色分析
- [ ] **洞察力**: 识别跨角色的深层次模式
- [ ] **可操作性**: 提供具体可执行的建议
- [ ] **平衡性**: 考虑所有角色的观点和关切
- [ ] **前瞻性**: 包含长期战略和创新考量
### 输出验证标准
- [ ] 推荐优先级基于多维度评估
- [ ] 实施计划考虑资源和时间约束
- [ ] 风险评估全面且有缓解策略
- [ ] 成功指标明确可测量
- [ ] 后续行动清晰具体

241
.claude/commands/workflow/brainstorm/system-architect.md Normal file
View File

@@ -0,0 +1,241 @@
---
name: brainstorm:system-architect
description: System architect perspective brainstorming for technical architecture and scalability analysis
usage: /brainstorm:system-architect <topic>
argument-hint: "topic or challenge to analyze from system architecture perspective"
examples:
- /brainstorm:system-architect "user authentication redesign"
- /brainstorm:system-architect "microservices migration strategy"
- /brainstorm:system-architect "system performance optimization"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🏗️ **角色定义: System Architect**
### 核心职责
- **技术架构设计**: 设计可扩展、可维护的系统架构
- **技术选型**: 评估和选择合适的技术栈和工具
- **系统集成**: 设计系统间的集成和通信机制
- **性能优化**: 识别性能瓶颈并提出优化方案
### 关注领域
- **可扩展性**: 系统容量规划、负载处理、弹性扩展
- **可靠性**: 高可用性、容错设计、灾难恢复
- **安全性**: 架构安全、数据保护、访问控制
- **维护性**: 代码质量、模块化设计、技术债务管理
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **架构设计**:
- 当前架构的优势和局限性是什么？
- 如何设计满足业务需求的技术架构？
- 微服务vs单体架构的权衡？
2. **技术选型**:
- 哪些技术栈最适合当前需求？
- 新技术的引入风险和收益？
- 团队技术能力与选型的匹配度？
3. **系统集成**:
- 系统间如何高效集成和通信？
- 第三方服务集成策略？
- API设计和版本管理？
4. **性能和扩展**:
- 系统性能瓶颈在哪里？
- 如何应对流量增长？
- 数据库扩展和优化策略？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建系统架构师分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
```
### Phase 3: TodoWrite 初始化
设置系统架构师视角分析的任务跟踪：
```json
[
{"content": "Initialize system architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze current system architecture", "status": "in_progress", "activeForm": "Analyzing architecture"},
{"content": "Evaluate technical requirements and constraints", "status": "pending", "activeForm": "Evaluating requirements"},
{"content": "Design optimal system architecture", "status": "pending", "activeForm": "Designing architecture"},
{"content": "Assess scalability and performance", "status": "pending", "activeForm": "Assessing scalability"},
{"content": "Plan technology stack and integration", "status": "pending", "activeForm": "Planning technology"},
{"content": "Generate comprehensive architecture documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct system architecture perspective brainstorming for: {topic}
ROLE CONTEXT: System Architect
- Focus Areas: Technical architecture, scalability, system integration, performance
- Analysis Framework: Architecture-first approach with scalability and maintainability focus
- Success Metrics: System performance, availability, maintainability, technical debt reduction
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. Current Architecture Assessment
- Analyze existing system architecture and identify pain points
- Evaluate current technology stack effectiveness
- Assess technical debt and maintenance overhead
- Identify architectural bottlenecks and limitations
2. Requirements and Constraints Analysis
- Define functional and non-functional requirements
- Identify performance, scalability, and availability requirements
- Analyze security and compliance constraints
- Assess resource and budget limitations
3. Architecture Design and Strategy
- Design optimal system architecture for the given requirements
- Recommend technology stack and architectural patterns
- Plan for microservices vs monolithic architecture decisions
- Design data architecture and storage strategies
4. Integration and Scalability Planning
- Design system integration patterns and APIs
- Plan for horizontal and vertical scaling strategies
- Design monitoring, logging, and observability systems
- Plan deployment and DevOps strategies
5. Risk Assessment and Mitigation
- Identify technical risks and failure points
- Design fault tolerance and disaster recovery strategies
- Plan for security vulnerabilities and mitigations
- Assess migration risks and strategies
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/system-architect/
- analysis.md (main architecture analysis)
- architecture-design.md (detailed system design and diagrams)
- technology-stack.md (technology recommendations and justifications)
- integration-plan.md (system integration and API strategies)
Apply system architecture expertise to generate scalable, maintainable, and performant solutions."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/system-architect/
├── analysis.md # 主要架构分析
├── architecture-design.md # 详细系统设计和图表
├── technology-stack.md # 技术栈建议和理由
└── integration-plan.md # 系统集成和API策略
```
### 文档模板
#### analysis.md 结构
```markdown
# System Architecture Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心架构发现和建议概述]
## Current State Assessment
### Existing Architecture Overview
### Technical Stack Analysis
### Performance Bottlenecks
### Technical Debt Assessment
## Requirements Analysis
### Functional Requirements
### Non-Functional Requirements
- Performance: [响应时间、吞吐量要求]
- Scalability: [用户量、数据量增长预期]
- Availability: [可用性要求]
- Security: [安全要求]
## Proposed Architecture
### High-Level Architecture Design
### Component Breakdown
### Data Flow Diagrams
### Technology Stack Recommendations
## Implementation Strategy
### Migration Planning
### Risk Mitigation
### Performance Optimization
### Security Considerations
## Scalability and Maintenance
### Horizontal Scaling Strategy
### Monitoring and Observability
### Deployment Strategy
### Long-term Maintenance Plan
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"system_architect": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/system-architect/",
"key_insights": ["scalability_bottleneck", "architecture_pattern", "technology_recommendation"]
}
}
}
}
```
### 与其他角色的协作
系统架构师视角为其他角色提供：
- **技术约束和可能性** → Product Manager
- **架构要求和限制** → UI Designer
- **数据架构需求** → Data Architect
- **安全架构框架** → Security Expert
- **技术实现框架** → Feature Planner
## ✅ **质量标准**
### 必须包含的分析元素
- [ ] 清晰的架构图和组件设计
- [ ] 详细的技术栈评估和推荐
- [ ] 可扩展性和性能分析
- [ ] 系统集成和API设计
- [ ] 风险评估和缓解策略
### 架构设计原则检查
- [ ] 可扩展性：系统能够处理增长
- [ ] 可维护性：代码结构清晰，易于修改
- [ ] 可靠性：具有容错和恢复机制
- [ ] 安全性：内置安全控制和保护
- [ ] 性能优化：满足响应时间和吞吐量要求
### 技术决策验证
- [ ] 技术选型有充分理由和对比分析
- [ ] 架构模式适合业务需求
- [ ] 集成方案考虑了兼容性和维护成本
- [ ] 部署策略可行且风险可控
- [ ] 监控和运维策略完整

251
.claude/commands/workflow/brainstorm/ui-designer.md Normal file
View File

@@ -0,0 +1,251 @@
---
name: brainstorm:ui-designer
description: UI designer perspective brainstorming for user experience and interface design analysis
usage: /brainstorm:ui-designer <topic>
argument-hint: "topic or challenge to analyze from UI/UX design perspective"
examples:
- /brainstorm:ui-designer "user authentication redesign"
- /brainstorm:ui-designer "mobile app navigation improvement"
- /brainstorm:ui-designer "accessibility enhancement strategy"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🎨 **角色定义: UI Designer**
### 核心职责
- **用户体验设计**: 创造直观、高效的用户体验
- **界面设计**: 设计美观、功能性的用户界面
- **交互设计**: 设计流畅的用户交互流程
- **可访问性设计**: 确保产品对所有用户友好
### 关注领域
- **用户体验**: 用户旅程、易用性、满意度、转化率
- **视觉设计**: 界面美学、品牌一致性、视觉层次
- **交互设计**: 操作流程、反馈机制、响应性能
- **可访问性**: WCAG标准、无障碍设计、包容性设计
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **用户需求和行为**:
- 用户在使用过程中的主要痛点是什么？
- 用户的期望和实际体验之间的差距？
- 不同用户群体的特殊需求？
2. **界面和交互设计**:
- 如何简化操作流程？
- 界面信息架构是否合理？
- 交互反馈是否及时和清晰？
3. **视觉和品牌**:
- 视觉设计是否支持品牌形象？
- 颜色、字体、布局的合理性？
- 跨平台一致性如何保证？
4. **技术和实现**:
- 设计的技术可行性？
- 响应式设计要求？
- 性能对用户体验的影响？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建UI设计师分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
```
### Phase 3: TodoWrite 初始化
设置UI设计师视角分析的任务跟踪：
```json
[
{"content": "Initialize UI designer brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze current user experience and pain points", "status": "in_progress", "activeForm": "Analyzing user experience"},
{"content": "Design user journey and interaction flows", "status": "pending", "activeForm": "Designing user flows"},
{"content": "Create visual design concepts and mockups", "status": "pending", "activeForm": "Creating visual concepts"},
{"content": "Evaluate accessibility and usability", "status": "pending", "activeForm": "Evaluating accessibility"},
{"content": "Plan responsive design strategy", "status": "pending", "activeForm": "Planning responsive design"},
{"content": "Generate comprehensive UI/UX documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct UI designer perspective brainstorming for: {topic}
ROLE CONTEXT: UI Designer
- Focus Areas: User experience, interface design, visual design, accessibility
- Analysis Framework: User-centered design approach with emphasis on usability and accessibility
- Success Metrics: User satisfaction, task completion rates, accessibility compliance, visual appeal
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. User Experience Analysis
- Identify current UX pain points and friction areas
- Map user journeys and identify optimization opportunities
- Analyze user behavior patterns and preferences
- Evaluate task completion flows and success rates
2. Interface Design Assessment
- Review current interface design and information architecture
- Identify visual hierarchy and navigation issues
- Assess consistency across different screens and states
- Evaluate mobile and desktop interface differences
3. Visual Design Strategy
- Develop visual design concepts aligned with brand guidelines
- Create color schemes, typography, and spacing systems
- Design iconography and visual elements
- Plan for dark mode and theme variations
4. Interaction Design Planning
- Design micro-interactions and animation strategies
- Plan feedback mechanisms and loading states
- Create error handling and validation UX
- Design responsive behavior and breakpoints
5. Accessibility and Inclusion
- Evaluate WCAG 2.1 compliance requirements
- Design for screen readers and assistive technologies
- Plan for color blindness and visual impairments
- Ensure keyboard navigation and focus management
6. Prototyping and Testing Strategy
- Plan for wireframes, mockups, and interactive prototypes
- Design user testing scenarios and success metrics
- Create A/B testing strategies for key interactions
- Plan for iterative design improvements
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
- analysis.md (main UI/UX analysis)
- design-system.md (visual design guidelines and components)
- user-flows.md (user journey maps and interaction flows)
- accessibility-plan.md (accessibility requirements and implementation)
Apply UI/UX design expertise to create user-centered, accessible, and visually appealing solutions."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
├── analysis.md # 主要UI/UX分析
├── design-system.md # 视觉设计指南和组件
├── user-flows.md # 用户旅程地图和交互流程
└── accessibility-plan.md # 可访问性要求和实现
```
### 文档模板
#### analysis.md 结构
```markdown
# UI Designer Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心UX发现和设计建议概述]
## Current UX Assessment
### User Pain Points
### Interface Issues
### Accessibility Gaps
### Performance Impact on UX
## User Experience Strategy
### Target User Personas
### User Journey Mapping
### Key Interaction Points
### Success Metrics
## Visual Design Approach
### Brand Alignment
### Color and Typography Strategy
### Layout and Spacing System
### Iconography and Visual Elements
## Interface Design Plan
### Information Architecture
### Navigation Strategy
### Component Library
### Responsive Design Approach
## Accessibility Implementation
### WCAG Compliance Plan
### Assistive Technology Support
### Inclusive Design Features
### Testing Strategy
## Prototyping and Validation
### Wireframe Strategy
### Interactive Prototype Plan
### User Testing Approach
### Iteration Framework
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"ui_designer": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/ui-designer/",
"key_insights": ["ux_improvement", "accessibility_requirement", "design_pattern"]
}
}
}
}
```
### 与其他角色的协作
UI设计师视角为其他角色提供：
- **用户界面要求** → System Architect
- **用户体验指标** → Product Manager
- **数据展示需求** → Data Architect
- **安全交互设计** → Security Expert
- **功能界面规范** → Feature Planner
## ✅ **质量标准**
### 必须包含的设计元素
- [ ] 详细的用户旅程分析
- [ ] 完整的界面设计方案
- [ ] 可访问性合规计划
- [ ] 响应式设计策略
- [ ] 可用性测试方案
### 设计原则检查
- [ ] 用户中心：设计以用户需求为核心
- [ ] 一致性：界面元素和交互保持一致
- [ ] 可访问性：符合WCAG无障碍标准
- [ ] 可用性：操作简单直观，学习成本低
- [ ] 美观性：视觉设计支持品牌和用户喜好
### UX评估指标
- [ ] 任务完成率和完成时间
- [ ] 用户满意度和净推荐值
- [ ] 错误率和恢复时间
- [ ] 可访问性合规得分
- [ ] 跨设备一致性评估

257
.claude/commands/workflow/brainstorm/user-researcher.md Normal file
View File

@@ -0,0 +1,257 @@
---
name: brainstorm:user-researcher
description: User researcher perspective brainstorming for user behavior analysis and research insights
usage: /brainstorm:user-researcher <topic>
argument-hint: "topic or challenge to analyze from user research perspective"
examples:
- /brainstorm:user-researcher "user onboarding experience"
- /brainstorm:user-researcher "mobile app usability issues"
- /brainstorm:user-researcher "feature adoption analysis"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🔍 **角色定义: User Researcher**
### 核心职责
- **用户行为研究**: 深度分析用户行为模式和动机
- **用户需求发现**: 通过研究发现未满足的用户需求
- **可用性评估**: 评估产品的可用性和用户体验问题
- **用户洞察生成**: 将研究发现转化为可操作的产品洞察
### 关注领域
- **用户行为**: 使用模式、决策路径、任务完成方式
- **用户需求**: 显性需求、隐性需求、情感需求
- **用户体验**: 痛点、满意度、情感反应、期望值
- **市场细分**: 用户画像、细分群体、使用场景
## 🧠 **分析框架**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **用户理解和洞察**:
- 目标用户的真实需求和痛点是什么？
- 用户的行为模式和使用场景？
- 不同用户群体的差异化需求？
2. **用户体验分析**:
- 当前用户体验的主要问题？
- 用户任务完成的障碍和摩擦点？
- 用户满意度和期望差距？
3. **研究方法和验证**:
- 哪些研究方法最适合当前问题？
- 如何验证假设和设计决策？
- 如何持续收集用户反馈？
4. **洞察转化和应用**:
- 研究发现如何转化为产品改进？
- 如何影响产品决策和设计？
- 如何建立以用户为中心的文化？
## ⚙️ **执行协议**
### Phase 1: 会话检测与初始化
```bash
# 自动检测活动会话
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
load_context_from(session_id)
ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
```bash
# 创建用户研究员分析目录
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
```
### Phase 3: TodoWrite 初始化
设置用户研究员视角分析的任务跟踪：
```json
[
{"content": "Initialize user researcher brainstorming session", "status": "completed", "activeForm": "Initializing session"},
{"content": "Analyze user behavior patterns and motivations", "status": "in_progress", "activeForm": "Analyzing user behavior"},
{"content": "Identify user needs and pain points", "status": "pending", "activeForm": "Identifying user needs"},
{"content": "Evaluate current user experience", "status": "pending", "activeForm": "Evaluating user experience"},
{"content": "Design user research methodology", "status": "pending", "activeForm": "Designing research methodology"},
{"content": "Generate user insights and recommendations", "status": "pending", "activeForm": "Generating insights"},
{"content": "Create comprehensive user research documentation", "status": "pending", "activeForm": "Creating documentation"}
]
```
### Phase 4: 概念规划代理协调
```bash
Task(conceptual-planning-agent): "
Conduct user researcher perspective brainstorming for: {topic}
ROLE CONTEXT: User Researcher
- Focus Areas: User behavior analysis, needs discovery, usability assessment, research methodology
- Analysis Framework: Human-centered research approach with emphasis on behavioral insights
- Success Metrics: User satisfaction, task success rates, insight quality, research impact
USER CONTEXT: {captured_user_requirements_from_session}
ANALYSIS REQUIREMENTS:
1. User Behavior Analysis
- Analyze current user behavior patterns and usage data
- Identify user decision-making processes and mental models
- Map user journeys and touchpoint interactions
- Assess user motivations and goals across different scenarios
- Identify behavioral segments and usage patterns
2. User Needs and Pain Points Discovery
- Conduct gap analysis between user needs and current solutions
- Identify unmet needs and latent requirements
- Analyze user feedback and support data for pain points
- Map emotional user journey and frustration points
- Prioritize needs based on user impact and frequency
3. Usability and Experience Assessment
- Evaluate current user experience against best practices
- Identify usability heuristics violations and UX issues
- Assess cognitive load and task completion efficiency
- Analyze accessibility barriers and inclusive design gaps
- Evaluate user satisfaction and Net Promoter Score trends
4. User Segmentation and Personas
- Define user segments based on behavior and needs
- Create detailed user personas with goals and contexts
- Map user scenarios and use case variations
- Analyze demographic and psychographic factors
- Identify key user archetypes and edge cases
5. Research Methodology Design
- Recommend appropriate research methods (qualitative/quantitative)
- Design user interview guides and survey instruments
- Plan usability testing scenarios and success metrics
- Design A/B testing strategies for key hypotheses
- Plan longitudinal research and continuous feedback loops
6. Insights Generation and Validation
- Synthesize research findings into actionable insights
- Identify opportunity areas and innovation potential
- Validate assumptions and hypotheses with evidence
- Prioritize insights based on business and user impact
- Create research-backed design principles and guidelines
OUTPUT REQUIREMENTS: Save comprehensive analysis to:
.workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
- analysis.md (main user research analysis)
- user-personas.md (detailed user personas and segments)
- research-plan.md (methodology and research approach)
- insights-recommendations.md (key findings and actionable recommendations)
Apply user research expertise to generate deep user understanding and actionable insights."
```
## 📊 **输出结构**
### 保存位置
```
.workflow/WFS-{topic-slug}/.brainstorming/user-researcher/
├── analysis.md # 主要用户研究分析
├── user-personas.md # 详细用户画像和细分
├── research-plan.md # 方法论和研究方法
└── insights-recommendations.md # 关键发现和可执行建议
```
### 文档模板
#### analysis.md 结构
```markdown
# User Researcher Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心用户研究发现和建议概述]
## Current User Landscape
### User Base Overview
### Behavioral Patterns
### Usage Statistics and Trends
### Satisfaction Metrics
## User Needs Analysis
### Primary User Needs
### Unmet Needs and Gaps
### Need Prioritization Matrix
### Emotional and Functional Needs
## User Experience Assessment
### Current UX Strengths
### Major Pain Points and Friction
### Usability Issues Identified
### Accessibility Gaps
## User Behavior Insights
### User Journey Mapping
### Decision-Making Patterns
### Task Completion Analysis
### Behavioral Segments
## Research Recommendations
### Recommended Research Methods
### Key Research Questions
### Success Metrics and KPIs
### Research Timeline and Resources
## Actionable Insights
### Immediate UX Improvements
### Product Feature Recommendations
### Long-term User Strategy
### Success Measurement Plan
```
## 🔄 **会话集成**
### 状态同步
分析完成后，更新 `workflow-session.json`:
```json
{
"phases": {
"BRAINSTORM": {
"user_researcher": {
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/user-researcher/",
"key_insights": ["user_behavior_pattern", "unmet_need", "usability_issue"]
}
}
}
}
```
### 与其他角色的协作
用户研究员视角为其他角色提供：
- **用户需求和洞察** → Product Manager
- **用户行为数据** → Data Architect
- **用户体验要求** → UI Designer
- **用户安全需求** → Security Expert
- **功能使用场景** → Feature Planner
## ✅ **质量标准**
### 必须包含的研究元素
- [ ] 详细的用户行为分析
- [ ] 明确的用户需求识别
- [ ] 全面的用户体验评估
- [ ] 科学的研究方法设计
- [ ] 可执行的改进建议
### 用户研究原则检查
- [ ] 以人为本：所有分析以用户为中心
- [ ] 基于证据：结论有数据和研究支撑
- [ ] 行为导向：关注实际行为而非声明意图
- [ ] 情境考虑：分析使用场景和环境因素
- [ ] 持续迭代：建立持续研究和改进机制
### 洞察质量评估
- [ ] 洞察的新颖性和深度
- [ ] 建议的可操作性和具体性
- [ ] 影响评估的准确性
- [ ] 研究方法的科学性
- [ ] 用户代表性的覆盖度