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

- Rewrite brainstorm commands to professional English with improved structure
- Add synthesis command for cross-role integration and recommendations
- Improve template reference format in gemini chat commands (remove backticks)
- Enhance clarity and organization across all brainstorm role files
- Standardize quality assurance sections and implementation protocols

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
catlog22
2025-09-09 09:04:39 +08:00
parent 3d521f0af1
commit 6f85340ab8
8 changed files with 667 additions and 583 deletions

View File

@@ -41,15 +41,15 @@ The bug-fix template provides structured analysis covering:
### 📚 **Context Assembly**
Context includes:
1. **Bug-Fix Template**: `@D:\Claude_dms3\.claude\prompt-templates\bug-fix.md`
2. **Project Guidelines**: `@{CLAUDE.md,**/*CLAUDE.md}`
1. **Bug-Fix Template**: @~/.claude/prompt-templates/bug-fix.md
2. **Project Guidelines**: @{CLAUDE.md,**/*CLAUDE.md}
3. **Relevant Files**: User-specified files or all files if `--all-files` used
### 📝 **Prompt Structure**
```
=== SYSTEM PROMPT ===
@D:\Claude_dms3\.claude\prompt-templates\bug-fix.md
@~/.claude/prompt-templates/bug-fix.md
=== CONTEXT ===
@{CLAUDE.md,**/*CLAUDE.md}
@@ -64,7 +64,7 @@ Context includes:
```pseudo
FUNCTION execute_bug_fix_analysis(bug_description, flags):
// Load bug-fix template
template = load_file("D:\Claude_dms3\.claude\prompt-templates\bug-fix.md")
template = load_file(@~/.claude/prompt-templates/bug-fix.md)
// Construct prompt with template
prompt = "=== SYSTEM PROMPT ===\n" + template + "\n\n"

View File

@@ -41,15 +41,15 @@ The planning template provides structured analysis covering:
### 📚 **Context Assembly**
Context includes:
1. **Planning Template**: `@D:\Claude_dms3\.claude\prompt-templates\plan.md`
2. **Project Guidelines**: `@{CLAUDE.md,**/*CLAUDE.md}`
1. **Planning Template**: @~/.claude/prompt-templates/plan.md
2. **Project Guidelines**: @{CLAUDE.md,**/*CLAUDE.md}
3. **Relevant Files**: User-specified files or all files if `--all-files` used
### 📝 **Prompt Structure**
```
=== SYSTEM PROMPT ===
@D:\Claude_dms3\.claude\prompt-templates\plan.md
@~/.claude/prompt-templates/plan.md
=== CONTEXT ===
@{CLAUDE.md,**/*CLAUDE.md}
@@ -64,7 +64,7 @@ Context includes:
```pseudo
FUNCTION execute_planning_analysis(planning_topic, flags):
// Load planning template
template = load_file("D:\Claude_dms3\.claude\prompt-templates\plan.md")
template = load_file(@~/.claude/prompt-templates/plan.md)
// Construct prompt with template
prompt = "=== SYSTEM PROMPT ===\n" + template + "\n\n"

View File

@@ -10,51 +10,61 @@ examples:
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 📊 **角色定义: Data Architect**
## 📊 **Role Overview: Data Architect**
### 核心职责
- **数据模型设计**: 设计高效、可扩展的数据模型
- **数据流程设计**: 规划数据采集、处理、存储流程
- **数据质量管理**: 确保数据准确性、完整性、一致性
- **分析和洞察**: 设计数据分析和商业智能解决方案
### Role Definition
Strategic data professional responsible for designing scalable, efficient data architectures that enable data-driven decision making through robust data models, processing pipelines, and analytics platforms.
### 关注领域
- **数据建模**: 关系模型、NoSQL、数据仓库、湖仓一体
- **数据管道**: ETL/ELT流程、实时处理、批处理
- **数据治理**: 数据质量、安全、隐私、合规
- **分析平台**: BI工具、机器学习、报表系统
### Core Responsibilities
- **Data Model Design**: Create efficient and scalable data models and schemas
- **Data Flow Design**: Plan data collection, processing, and storage workflows
- **Data Quality Management**: Ensure data accuracy, completeness, and consistency
- **Analytics and Insights**: Design data analysis and business intelligence solutions
## 🧠 **分析框架**
### Focus Areas
- **Data Modeling**: Relational models, NoSQL, data warehouses, lakehouse architectures
- **Data Pipelines**: ETL/ELT processes, real-time processing, batch processing
- **Data Governance**: Data quality, security, privacy, compliance frameworks
- **Analytics Platforms**: BI tools, machine learning infrastructure, reporting systems
### Success Metrics
- Data quality and consistency metrics
- Processing performance and throughput
- Analytics accuracy and business impact
- Data governance and compliance adherence
## 🧠 **Analysis Framework**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **数据需求和来源**:
- 需要哪些数据来支持业务决策?
- 数据来源的可靠性和质量如何?
- 实时数据vs历史数据的需求平衡
### Key Analysis Questions
2. **数据架构和存储**:
- 最适合的数据存储方案是什么?
- 如何设计可扩展的数据模型?
- 数据分区和索引策略?
**1. Data Requirements and Sources**
- What data is needed to support business decisions and analytics?
- How reliable and high-quality are the available data sources?
- What is the balance between real-time and historical data needs?
3. **数据处理和流程**:
- 数据处理的性能要求?
- 如何设计容错的数据管道?
- 数据变更和版本控制策略?
**2. Data Architecture and Storage**
- What is the most appropriate data storage solution for requirements?
- How should we design scalable and maintainable data models?
- What are the optimal data partitioning and indexing strategies?
4. **分析和报告**:
- 如何支持不同的分析需求?
- 实时仪表板vs定期报告
- 数据可视化和自助分析能力?
**3. Data Processing and Workflows**
- What are the performance requirements for data processing?
- How should we design fault-tolerant and resilient data pipelines?
- What data versioning and change management strategies are needed?
## ⚙️ **执行协议**
**4. Analytics and Reporting**
- How can we support diverse analytical requirements and use cases?
- What balance between real-time dashboards and periodic reports is optimal?
- What self-service analytics and data visualization capabilities are needed?
### Phase 1: 会话检测与初始化
## ⚙️ **Execution Protocol**
### Phase 1: Session Detection & Initialization
```bash
# 自动检测活动会话
# Detect active workflow session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
@@ -63,14 +73,14 @@ ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
### Phase 2: Directory Structure Creation
```bash
# 创建数据架构师分析目录
# Create data architect analysis directory
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/data-architect/
```
### Phase 3: TodoWrite 初始化
设置数据架构师视角分析的任务跟踪:
### Phase 3: Task Tracking Initialization
Initialize data architect perspective analysis tracking:
```json
[
{"content": "Initialize data architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
@@ -83,7 +93,7 @@ mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/data-architect/
]
```
### Phase 4: 概念规划代理协调
### Phase 4: Conceptual Planning Agent Coordination
```bash
Task(conceptual-planning-agent): "
Conduct data architect perspective brainstorming for: {topic}
@@ -98,114 +108,112 @@ 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
- Define data collection requirements and constraints
- Analyze data volume, velocity, and variety characteristics
- Map data lineage and dependencies across systems
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
2. Data Model and Schema Design
- Design logical and physical data models for optimal performance
- Plan database schemas, indexes, and partitioning strategies
- Design data relationships and referential integrity constraints
- Plan for data archival, retention, and lifecycle management
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
3. Data Pipeline Architecture
- Design ETL/ELT processes for data ingestion and transformation
- Plan real-time and batch processing workflows
- Design error handling, monitoring, and alerting mechanisms
- Plan for data pipeline scalability and performance optimization
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
- Establish data quality metrics and validation rules
- Design data governance policies and procedures
- Plan data security, privacy, and compliance frameworks
- Create data cataloging and metadata management strategies
5. Analytics and Reporting Infrastructure
- Design data warehouse/data mart architecture
- Plan business intelligence and reporting solutions
- Design self-service analytics capabilities
5. Analytics and Business Intelligence
- Design data warehouse and data mart architectures
- Plan for OLAP cubes, reporting, and dashboard requirements
- Design self-service analytics and data exploration 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
6. Performance and Scalability Planning
- Analyze current and projected data volumes and growth
- Design horizontal and vertical scaling strategies
- Plan for high availability and disaster recovery
- Optimize query performance and resource utilization
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)
- data-model.md (data models, schemas, and relationships)
- pipeline-design.md (data processing and ETL/ELT workflows)
- governance-plan.md (data quality, security, and governance)
Apply data architecture expertise to create scalable, reliable, and insightful data solutions."
```
## 📊 **输出结构**
## 📊 **Output Specification**
### 保存位置
### Output Location
```
.workflow/WFS-{topic-slug}/.brainstorming/data-architect/
├── analysis.md # 主要数据架构分析
├── data-model.md # 详细数据模型和架构
├── pipeline-design.md # 数据处理工作流和ETL设计
└── governance-plan.md # 数据质量、安全和合规框架
├── analysis.md # Primary data architecture analysis
├── data-model.md # Data models, schemas, and relationships
├── pipeline-design.md # Data processing and ETL/ELT workflows
└── governance-plan.md # Data quality, security, and governance
```
### 文档模板
### Document Templates
#### analysis.md 结构
#### analysis.md Structure
```markdown
# Data Architect Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心数据架构发现和建议概述]
[Key data architecture findings and recommendations overview]
## Current Data Landscape Assessment
## Current Data Landscape
### Existing Data Sources
### Data Quality Issues
### Current Data Architecture
### Data Quality Assessment
### Performance Bottlenecks
### Integration Challenges
## Data Requirements Analysis
### Business Data Requirements
### Business Data Needs
### Technical Data Requirements
- Volume: [预期数据量和增长]
- Velocity: [数据更新频率]
- Variety: [数据类型和格式]
- Veracity: [数据质量要求]
### Data Volume and Growth Projections
### Real-time vs Batch Processing Needs
## Proposed Data Architecture
### Data Storage Strategy
### Data Model Design
### Integration Architecture
### Analytics Infrastructure
### Storage Architecture
### Processing Pipeline Design
### Integration Patterns
## Data Pipeline Design
### Data Ingestion Strategy
### Processing Workflows
### Transformation Rules
### Quality Assurance
## Governance and Compliance
## Data Quality and Governance
### Data Quality Framework
### Security and Privacy
### Audit and Lineage
### Governance Policies
### Security and Privacy Controls
### Compliance Requirements
## Performance and Scalability
### Optimization Strategies
### Scaling Plans
### Monitoring and Alerting
### Disaster Recovery
## Analytics and Reporting Strategy
### Business Intelligence Architecture
### Self-Service Analytics Design
### Performance Monitoring
### Scalability Planning
## Implementation Roadmap
### Migration Strategy
### Technology Stack Recommendations
### Resource Requirements
### Risk Mitigation Plan
```
## 🔄 **会话集成**
## 🔄 **Session Integration**
### 状态同步
分析完成后,更新 `workflow-session.json`:
### Status Synchronization
Upon completion, update `workflow-session.json`:
```json
{
"phases": {
@@ -214,40 +222,47 @@ Apply data architecture expertise to create scalable, reliable, and insightful d
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/data-architect/",
"key_insights": ["data_model_optimization", "pipeline_efficiency", "governance_requirement"]
"key_insights": ["data_model_optimization", "pipeline_architecture", "analytics_strategy"]
}
}
}
}
```
### 与其他角色的协作
数据架构师视角为其他角色提供:
- **数据能力和限制** → Product Manager
- **数据存储要求** → System Architect
- **数据展示能力** → UI Designer
- **数据安全要求** → Security Expert
- **功能数据支持** → Feature Planner
### Cross-Role Collaboration
Data architect perspective provides:
- **Data Storage Requirements** → System Architect
- **Analytics Data Requirements** → Product Manager
- **Data Visualization Specifications** → UI Designer
- **Data Security Framework** → Security Expert
- **Feature Data Requirements** → Feature Planner
## ✅ **质量标准**
## ✅ **Quality Assurance**
### 必须包含的架构元素
- [ ] 完整的数据模型设计
- [ ] 详细的数据流程图
- [ ] 数据质量保证方案
- [ ] 可扩展性和性能优化
- [ ] 合规和安全控制
### Required Architecture Elements
- [ ] Comprehensive data model with clear relationships and constraints
- [ ] Scalable data pipeline design with error handling and monitoring
- [ ] Data quality framework with validation rules and metrics
- [ ] Governance plan addressing security, privacy, and compliance
- [ ] Analytics architecture supporting business intelligence needs
### 数据架构原则检查
- [ ] 可扩展性:支持数据量和用户增长
- [ ] 可靠性:具有容错和恢复机制
- [ ] 可维护性:清晰的数据模型和流程
- [ ] 安全性:数据保护和访问控制
- [ ] 高效性:优化的查询和处理性能
### Data Architecture Principles
- [ ] **Scalability**: Architecture can handle data volume and velocity growth
- [ ] **Quality**: Built-in data validation, cleansing, and quality monitoring
- [ ] **Security**: Data protection, access controls, and privacy compliance
- [ ] **Performance**: Optimized for query performance and processing efficiency
- [ ] **Maintainability**: Clear data lineage, documentation, and change management
### 数据质量指标
- [ ] 数据准确性和完整性标准
- [ ] 数据一致性检查机制
- [ ] 数据时效性和新鲜度要求
- [ ] 数据可追溯性和审计能力
- [ ] 合规性检查和报告机制
### Implementation Validation
- [ ] **Technical Feasibility**: All proposed solutions are technically achievable
- [ ] **Performance Requirements**: Architecture meets processing and query performance needs
- [ ] **Cost Effectiveness**: Storage and processing costs are optimized and sustainable
- [ ] **Governance Compliance**: Meets regulatory and organizational data requirements
- [ ] **Future Readiness**: Design accommodates anticipated growth and changing needs
### Data Quality Standards
- [ ] **Accuracy**: Data validation rules ensure correctness and consistency
- [ ] **Completeness**: Strategies for handling missing data and ensuring coverage
- [ ] **Timeliness**: Data freshness requirements met through appropriate processing
- [ ] **Consistency**: Data definitions and formats standardized across systems
- [ ] **Lineage**: Complete data lineage tracking from source to consumption

View File

@@ -10,51 +10,61 @@ examples:
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🎯 **角色定义: Product Manager**
## 🎯 **Role Overview: Product Manager**
### 核心职责
- **用户需求分析**: 深度理解用户痛点和需求
- **商业价值评估**: 评估功能和改进的商业影响
- **市场定位**: 分析竞争环境和市场机会
- **产品战略**: 制定产品路线图和优先级
### Role Definition
Strategic product leader focused on maximizing user value and business impact through data-driven decisions and market-oriented thinking.
### 关注领域
- **用户体验**: 用户旅程、满意度、转化率
- **商业指标**: ROI、用户增长、留存率、收入影响
- **市场竞争**: 竞品分析、差异化优势、市场趋势
- **产品生命周期**: 功能演进、技术债务、可维护性
### Core Responsibilities
- **User Needs Analysis**: Identify and validate genuine user problems and requirements
- **Business Value Assessment**: Quantify commercial impact and return on investment
- **Market Positioning**: Analyze competitive landscape and identify opportunities
- **Product Strategy**: Develop roadmaps, priorities, and go-to-market approaches
## 🧠 **分析框架**
### Focus Areas
- **User Experience**: Journey mapping, satisfaction metrics, conversion optimization
- **Business Metrics**: ROI, user growth, retention rates, revenue impact
- **Market Dynamics**: Competitive analysis, differentiation, market trends
- **Product Lifecycle**: Feature evolution, technical debt management, scalability
### Success Metrics
- User satisfaction scores and engagement metrics
- Business KPIs (revenue, growth, retention)
- Market share and competitive positioning
- Product adoption and feature utilization rates
## 🧠 **Analysis Framework**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **用户价值**:
- 这个功能/改进解决了什么真实问题?
- 目标用户群体是谁?他们的核心需求是什么?
- 用户愿意为此付费/投入时间吗?
### Key Analysis Questions
2. **商业影响**:
- 预期的商业收益是什么?
- 实施成本vs预期回报如何
- 对现有业务流程有何影响?
**1. User Value Assessment**
- What genuine user problem does this solve?
- Who are the target users and what are their core needs?
- How does this improve the user experience measurably?
3. **市场机会**:
- 市场上现有解决方案的不足在哪?
- 我们的差异化优势是什么?
- 时机是否合适?
**2. Business Impact Evaluation**
- What are the expected business outcomes?
- How does the cost-benefit analysis look?
- What impact will this have on existing workflows?
4. **执行可行性**:
- 所需资源和时间估算?
- 技术可行性和风险评估?
- 团队能力匹配度?
**3. Market Opportunity Analysis**
- What gaps exist in current market solutions?
- What is our unique competitive advantage?
- Is the timing right for this initiative?
## ⚙️ **执行协议**
**4. Execution Feasibility**
- What resources and timeline are required?
- What are the technical and market risks?
- Do we have the right team capabilities?
### Phase 1: 会话检测与初始化
## ⚙️ **Execution Protocol**
### Phase 1: Session Detection & Initialization
```bash
# 自动检测活动会话
# Detect active workflow session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
@@ -63,14 +73,14 @@ ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
### Phase 2: Directory Structure Creation
```bash
# 创建产品经理分析目录
# Create product manager analysis directory
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/product-manager/
```
### Phase 3: TodoWrite 初始化
设置产品经理视角分析的任务跟踪:
### Phase 3: Task Tracking Initialization
Initialize product manager perspective analysis tracking:
```json
[
{"content": "Initialize product manager brainstorming session", "status": "completed", "activeForm": "Initializing session"},
@@ -83,7 +93,7 @@ mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/product-manager/
]
```
### Phase 4: 概念规划代理协调
### Phase 4: Conceptual Planning Agent Coordination
```bash
Task(conceptual-planning-agent): "
Conduct product management perspective brainstorming for: {topic}
@@ -130,26 +140,26 @@ OUTPUT REQUIREMENTS: Save comprehensive analysis to:
Apply product management expertise to generate actionable insights addressing business goals and user needs."
```
## 📊 **输出结构**
## 📊 **Output Specification**
### 保存位置
### Output Location
```
.workflow/WFS-{topic-slug}/.brainstorming/product-manager/
├── analysis.md # 主要产品分析
├── business-case.md # 商业论证和指标
├── user-research.md # 用户研究和市场洞察
└── roadmap.md # 战略建议和时间线
├── analysis.md # Primary product management analysis
├── business-case.md # Business justification and metrics
├── user-research.md # User research and market insights
└── roadmap.md # Strategic recommendations and timeline
```
### 文档模板
### Document Templates
#### analysis.md 结构
#### analysis.md Structure
```markdown
# Product Manager Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心发现和建议概述]
[Key findings and recommendations overview]
## User Needs Analysis
### Target User Segments
@@ -174,10 +184,10 @@ Apply product management expertise to generate actionable insights addressing bu
### Long-term Vision (12+ months)
```
## 🔄 **会话集成**
## 🔄 **Session Integration**
### 状态同步
分析完成后,更新 `workflow-session.json`:
### Status Synchronization
Upon completion, update `workflow-session.json`:
```json
{
"phases": {
@@ -186,32 +196,40 @@ Apply product management expertise to generate actionable insights addressing bu
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/product-manager/",
"key_insights": ["insight1", "insight2", "insight3"]
"key_insights": ["user_value_proposition", "business_impact_assessment", "strategic_recommendations"]
}
}
}
}
```
### 与其他角色的协作
产品经理视角为其他角色提供:
- **用户需求定义** → UI Designer
- **业务约束和目标** → System Architect
- **功能优先级** → Feature Planner
- **市场要求** → Innovation Lead
### Cross-Role Collaboration
Product manager perspective provides:
- **User Requirements Definition** → UI Designer
- **Business Constraints and Objectives** → System Architect
- **Feature Prioritization** → Feature Planner
- **Market Requirements** → Innovation Lead
- **Success Metrics** → Business Analyst
## ✅ **质量标准**
## ✅ **Quality Assurance**
### 必须包含的分析元素
- [ ] 明确的用户价值主张
- [ ] 量化的业务影响评估
- [ ] 可执行的产品策略建议
- [ ] 基于数据的优先级排序
- [ ] 清晰的成功指标定义
### Required Analysis Elements
- [ ] Clear user value proposition with supporting evidence
- [ ] Quantified business impact assessment with metrics
- [ ] Actionable product strategy recommendations
- [ ] Data-driven priority rankings
- [ ] Well-defined success criteria and KPIs
### 输出质量检查
- [ ] 分析基于真实用户需求
- [ ] 商业论证逻辑清晰
- [ ] 建议具有可操作性
- [ ] 时间线合理可行
- [ ] 风险识别全面准确
### Output Quality Standards
- [ ] Analysis grounded in real user needs and market data
- [ ] Business justification with clear logic and assumptions
- [ ] Recommendations are specific and actionable
- [ ] Timeline and milestones are realistic and achievable
- [ ] Risk identification is comprehensive and accurate
### Product Management Principles
- [ ] **User-Centric**: All decisions prioritize user value and experience
- [ ] **Data-Driven**: Conclusions supported by metrics and research
- [ ] **Market-Aware**: Considers competitive landscape and trends
- [ ] **Business-Focused**: Aligns with commercial objectives and constraints
- [ ] **Execution-Ready**: Provides clear next steps and success measures

View File

@@ -2,59 +2,69 @@
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"
argument-hint: "topic or challenge to analyze from cybersecurity perspective"
examples:
- /brainstorm:security-expert "user authentication security"
- /brainstorm:security-expert "user authentication security review"
- /brainstorm:security-expert "API security architecture"
- /brainstorm:security-expert "data privacy compliance"
- /brainstorm:security-expert "data protection compliance strategy"
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🔒 **角色定义: Security Expert**
## 🔒 **Role Overview: Security Expert**
### 核心职责
- **威胁建模**: 识别和评估安全威胁和攻击向量
- **安全架构**: 设计防御性安全控制和保护机制
- **合规评估**: 确保符合安全标准和法规要求
- **风险管理**: 评估和缓解安全风险
### Role Definition
Cybersecurity specialist focused on identifying threats, designing security controls, and ensuring comprehensive protection of systems, data, and users through proactive security architecture and risk management.
### 关注领域
- **应用安全**: 代码安全、输入验证、会话管理
- **基础设施安全**: 网络安全、服务器加固、云安全
- **数据保护**: 数据加密、访问控制、隐私保护
- **合规管理**: GDPR、SOC2、ISO27001、行业标准
### Core Responsibilities
- **Threat Modeling**: Identify and analyze potential security threats and attack vectors
- **Security Architecture**: Design robust security controls and defensive measures
- **Risk Assessment**: Evaluate security risks and develop mitigation strategies
- **Compliance Management**: Ensure adherence to security standards and regulations
## 🧠 **分析框架**
### Focus Areas
- **Application Security**: Code security, input validation, authentication, authorization
- **Infrastructure Security**: Network security, system hardening, access controls
- **Data Protection**: Encryption, privacy controls, data classification, compliance
- **Operational Security**: Monitoring, incident response, security awareness, procedures
### Success Metrics
- Vulnerability reduction and remediation rates
- Security incident prevention and response times
- Compliance audit results and regulatory adherence
- Security awareness and training effectiveness
## 🧠 **Analysis Framework**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **威胁识别和建模**:
- 主要的安全威胁和攻击向量是什么?
- 资产价值和风险评估?
- 攻击者画像和攻击路径分析?
### Key Analysis Questions
2. **安全控制和防护**:
- 需要实施哪些安全控制?
- 身份认证和授权机制?
- 数据保护和加密策略?
**1. Threat Landscape Assessment**
- What are the primary threat vectors and attack scenarios?
- Who are the potential threat actors and what are their motivations?
- What are the current vulnerabilities and exposure risks?
3. **合规和标准**:
- 适用的合规要求和标准?
- 安全审计和监控需求?
- 事件响应和恢复计划?
**2. Security Architecture Design**
- What security controls and defensive measures are needed?
- How should we implement defense-in-depth strategies?
- What authentication and authorization mechanisms are appropriate?
4. **风险评估和缓解**:
- 安全风险等级和影响评估?
- 风险缓解策略和优先级?
- 持续监控和改进机制?
**3. Risk Management and Compliance**
- What are the regulatory and compliance requirements?
- How should we prioritize and manage identified security risks?
- What security policies and procedures need to be established?
## ⚙️ **执行协议**
**4. Implementation and Operations**
- How should we integrate security into development and operations?
- What monitoring and detection capabilities are required?
- How should we plan for incident response and recovery?
### Phase 1: 会话检测与初始化
## ⚙️ **Execution Protocol**
### Phase 1: Session Detection & Initialization
```bash
# 自动检测活动会话
# Detect active workflow session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
@@ -63,157 +73,147 @@ ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
### Phase 2: Directory Structure Creation
```bash
# 创建安全专家分析目录
# Create security expert analysis directory
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/security-expert/
```
### Phase 3: TodoWrite 初始化
设置安全专家视角分析的任务跟踪:
### Phase 3: Task Tracking Initialization
Initialize security expert perspective analysis tracking:
```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": "Evaluate compliance and regulatory requirements", "status": "pending", "activeForm": "Evaluating compliance"},
{"content": "Plan security implementation and integration", "status": "pending", "activeForm": "Planning implementation"},
{"content": "Design monitoring and incident response", "status": "pending", "activeForm": "Designing monitoring"},
{"content": "Generate comprehensive security documentation", "status": "pending", "activeForm": "Generating documentation"}
]
```
### Phase 4: 概念规划代理协调
### Phase 4: Conceptual Planning Agent Coordination
```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
- Focus Areas: Threat modeling, security architecture, risk management, compliance
- Analysis Framework: Security-first approach with emphasis on defense-in-depth and risk mitigation
- Success Metrics: Vulnerability reduction, incident prevention, compliance adherence, security maturity
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
- Identify potential threat actors and their capabilities
- Map attack vectors and potential attack paths
- Analyze system vulnerabilities and exposure points
- Assess business impact and likelihood of security incidents
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
- Plan encryption and data protection strategies
- Design network security and access controls
- Plan 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
3. Application Security Analysis
- Review secure coding practices and input validation
- Analyze session management and state security
- Assess API security and integration points
- Plan for secure software development lifecycle
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
4. Infrastructure and Operations Security
- Design system hardening and configuration management
- Plan security monitoring and SIEM integration
- Design incident response and recovery procedures
- Plan security awareness and training programs
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
5. Compliance and Regulatory Analysis
- Identify applicable compliance frameworks (GDPR, SOX, PCI-DSS, etc.)
- Map security controls to regulatory requirements
- Plan compliance monitoring and audit procedures
- Design privacy protection and data handling policies
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
6. Security Implementation Planning
- Prioritize security controls based on risk assessment
- Plan phased security implementation approach
- Design security testing and validation procedures
- Plan ongoing security maintenance and updates
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)
- security-architecture.md (security controls and defensive measures)
- compliance-plan.md (regulatory compliance and policy framework)
- implementation-guide.md (security implementation and operational procedures)
Apply security expertise to create robust, compliant, and resilient security solutions."
Apply cybersecurity expertise to create comprehensive security solutions that protect against threats while enabling business objectives."
```
## 📊 **输出结构**
## 📊 **Output Specification**
### 保存位置
### Output Location
```
.workflow/WFS-{topic-slug}/.brainstorming/security-expert/
├── analysis.md # 主要安全分析和威胁建模
├── security-architecture.md # 详细安全控制和架构
├── compliance-framework.md # 法规要求和合规计划
└── incident-response.md # 安全事件管理和恢复程序
├── analysis.md # Primary security analysis and threat modeling
├── security-architecture.md # Security controls and defensive measures
├── compliance-plan.md # Regulatory compliance and policy framework
└── implementation-guide.md # Security implementation and operational procedures
```
### 文档模板
### Document Templates
#### analysis.md 结构
#### analysis.md Structure
```markdown
# Security Expert Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心安全发现和建议概述]
[Key security findings and recommendations overview]
## Threat Modeling
### Threat Actors
- Internal threats: [内部威胁分析]
- External threats: [外部威胁分析]
- Threat capabilities and motivations
## Threat Landscape Assessment
### Threat Actor Analysis
### Attack Vector Identification
### Vulnerability Assessment
### Risk Prioritization Matrix
### Attack Vectors
### Attack Surface Analysis
### Risk Assessment Matrix
## Security Requirements Analysis
### Functional Security Requirements
### Compliance and Regulatory Requirements
### Business Continuity Requirements
### Privacy and Data Protection Needs
## Current Security Posture
### Existing Security Controls
### Identified Vulnerabilities
### Security Gaps and Weaknesses
### Compliance Status
## Security Architecture Design
### Authentication and Authorization Framework
### Data Protection and Encryption Strategy
### Network Security and Access Controls
### Monitoring and Detection Capabilities
## Security Architecture Recommendations
### Authentication and Authorization
### Data Protection Strategy
### Network Security Design
### Application Security Controls
## Risk Management Strategy
### Risk Assessment Methodology
### Risk Mitigation Controls
### Residual Risk Acceptance Criteria
### Continuous Risk Monitoring Plan
## Risk Management
### Critical Risks Identified
### Risk Mitigation Strategies
### Security Control Prioritization
### Residual Risk Assessment
## Implementation Security Plan
### Security Control Implementation Priorities
### Security Testing and Validation Approach
### Incident Response and Recovery Procedures
### Security Awareness and Training Program
## 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
## Compliance and Governance
### Regulatory Compliance Framework
### Security Policy and Procedure Requirements
### Audit and Assessment Planning
### Governance and Oversight Structure
```
## 🔄 **会话集成**
## 🔄 **Session Integration**
### 状态同步
分析完成后,更新 `workflow-session.json`:
### Status Synchronization
Upon completion, update `workflow-session.json`:
```json
{
"phases": {
@@ -222,40 +222,47 @@ Apply security expertise to create robust, compliant, and resilient security sol
"status": "completed",
"completed_at": "timestamp",
"output_directory": ".workflow/WFS-{topic}/.brainstorming/security-expert/",
"key_insights": ["critical_vulnerability", "compliance_requirement", "security_control"]
"key_insights": ["threat_model", "security_controls", "compliance_requirements"]
}
}
}
}
```
### 与其他角色的协作
安全专家视角为其他角色提供:
- **安全要求和约束** → System Architect
- **安全合规影响** → Product Manager
- **安全用户体验** → UI Designer
- **数据安全要求** → Data Architect
- **安全功能需求** → Feature Planner
### Cross-Role Collaboration
Security expert perspective provides:
- **Security Architecture Requirements** → System Architect
- **Security Compliance Constraints** → Product Manager
- **Secure Interface Design Requirements** → UI Designer
- **Data Protection Requirements** → Data Architect
- **Security Feature Specifications** → Feature Planner
## ✅ **质量标准**
## ✅ **Quality Assurance**
### 必须包含的安全元素
- [ ] 全面的威胁模型和风险评估
- [ ] 详细的安全架构和控制设计
- [ ] 合规要求映射和实施计划
- [ ] 事件响应和恢复程序
- [ ] 安全监控和测试策略
### Required Security Elements
- [ ] Comprehensive threat model with identified attack vectors and mitigations
- [ ] Security architecture design with layered defensive controls
- [ ] Risk assessment with prioritized mitigation strategies
- [ ] Compliance framework addressing all relevant regulatory requirements
- [ ] Implementation plan with security testing and validation procedures
### 安全框架检查
- [ ] 防御深度:多层安全控制
- [ ] 最小权限:访问控制最小化
- [ ] 失败安全:安全失败时的默认行为
- [ ] 完整监控:全面的安全日志和告警
- [ ] 持续改进:定期安全评估和更新
### Security Architecture Principles
- [ ] **Defense-in-Depth**: Multiple layers of security controls and protective measures
- [ ] **Least Privilege**: Minimal access rights granted based on need-to-know basis
- [ ] **Zero Trust**: Verify and validate all access requests regardless of location
- [ ] **Security by Design**: Security considerations integrated from initial design phase
- [ ] **Fail Secure**: System failures default to secure state with controlled recovery
### 威胁覆盖验证
- [ ] OWASP Top 10 威胁评估
- [ ] 内部和外部威胁分析
- [ ] 供应链安全风险
- [ ] 云安全和配置管理
- [ ] 隐私和数据保护合规
### Risk Management Standards
- [ ] **Threat Coverage**: All identified threats have corresponding mitigation controls
- [ ] **Risk Tolerance**: Security risks align with organizational risk appetite
- [ ] **Continuous Monitoring**: Ongoing security monitoring and threat detection capabilities
- [ ] **Incident Response**: Comprehensive incident response and recovery procedures
- [ ] **Compliance Adherence**: Full compliance with applicable regulatory frameworks
### Implementation Readiness
- [ ] **Control Effectiveness**: Security controls are tested and validated for effectiveness
- [ ] **Integration Planning**: Security solutions integrate with existing infrastructure
- [ ] **Operational Procedures**: Clear procedures for security operations and maintenance
- [ ] **Training and Awareness**: Security awareness programs for all stakeholders
- [ ] **Continuous Improvement**: Framework for ongoing security assessment and enhancement

View File

@@ -8,30 +8,33 @@ examples:
allowed-tools: Read(*), Write(*), TodoWrite(*), Glob(*)
---
## 🧩 **命令定义: Brainstorm Synthesis**
## 🧩 **Command Overview: Brainstorm Synthesis**
### 核心功能
- **跨角色综合**: 整合所有角色的头脑风暴分析结果
- **洞察提炼**: 识别共识点、分歧点和创新机会
- **决策支持**: 生成优先级建议和行动计划
- **报告生成**: 创建综合性的头脑风暴总结报告
### Core Function
Cross-role integration command that synthesizes all brainstorming role perspectives into comprehensive strategic analysis, actionable recommendations, and prioritized implementation roadmaps.
### 分析范围
- **产品管理**: 用户需求、商业价值、市场机会
- **技术架构**: 系统设计、技术选型、实施可行性
- **用户体验**: 界面设计、可用性、可访问性
- **数据架构**: 数据模型、处理流程、分析能力
- **安全专家**: 威胁评估、安全控制、合规要求
- **用户研究**: 行为洞察、需求验证、体验优化
- **业务分析**: 流程优化、成本效益、变更管理
- **创新领导**: 技术趋势、创新机会、未来规划
- **功能规划**: 开发计划、质量保证、交付管理
### Primary Capabilities
- **Cross-Role Integration**: Consolidate analysis results from all brainstorming role perspectives
- **Insight Synthesis**: Identify consensus areas, disagreement points, and breakthrough opportunities
- **Decision Support**: Generate prioritized recommendations and strategic action plans
- **Comprehensive Reporting**: Create integrated brainstorming summary reports with implementation guidance
## ⚙️ **执行协议**
### Analysis Scope Coverage
- **Product Management**: User needs, business value, market opportunities
- **System Architecture**: Technical design, technology selection, implementation feasibility
- **User Experience**: Interface design, usability, accessibility standards
- **Data Architecture**: Data models, processing workflows, analytics capabilities
- **Security Expert**: Threat assessment, security controls, compliance requirements
- **User Research**: Behavioral insights, needs validation, experience optimization
- **Business Analysis**: Process optimization, cost-benefit analysis, change management
- **Innovation Leadership**: Technology trends, innovation opportunities, future planning
- **Feature Planning**: Development planning, quality assurance, delivery management
### Phase 1: 会话检测与数据收集
## ⚙️ **Execution Protocol**
### Phase 1: Session Detection & Data Collection
```bash
# 自动检测活动会话
# Detect active brainstorming session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
@@ -41,9 +44,9 @@ ELSE:
EXIT
```
### Phase 2: 角色输出扫描
### Phase 2: Role Output Scanning
```bash
# 扫描所有角色的头脑风暴输出
# Scan all role brainstorming outputs
SCAN_DIRECTORY: .workflow/WFS-{session}/.brainstorming/
COLLECT_OUTPUTS: [
product-manager/analysis.md,
@@ -58,11 +61,11 @@ COLLECT_OUTPUTS: [
]
```
### Phase 3: TodoWrite 初始化
设置综合分析任务跟踪:
### Phase 3: Task Tracking Initialization
Initialize synthesis analysis task tracking:
```json
[
{"content": "Initialize synthesis brainstorming session", "status": "completed", "activeForm": "Initializing synthesis"},
{"content": "Initialize brainstorming synthesis 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"},
@@ -72,9 +75,9 @@ COLLECT_OUTPUTS: [
]
```
### Phase 4: 综合分析执行
### Phase 4: Cross-Role Analysis Execution
#### 4.1 数据收集和预处理
#### 4.1 Data Collection and Preprocessing
```pseudo
FOR each role_directory in brainstorming_roles:
IF role_directory exists:
@@ -87,27 +90,27 @@ FOR each role_directory in brainstorming_roles:
END FOR
```
#### 4.2 跨角色洞察分析
#### 4.2 Cross-Role Insight Analysis
```pseudo
# 共识点识别
# Consensus identification
consensus_areas = identify_common_themes(role_insights)
agreement_matrix = create_agreement_matrix(role_recommendations)
# 分歧点分析
# Disagreement analysis
disagreement_areas = identify_conflicting_views(role_insights)
tension_points = analyze_role_conflicts(role_recommendations)
# 创新机会提取
# Innovation opportunity extraction
innovation_opportunities = extract_breakthrough_ideas(role_insights)
synergy_opportunities = identify_cross_role_synergies(role_insights)
```
#### 4.3 优先级和决策矩阵生成
#### 4.3 Priority and Decision Matrix Generation
```pseudo
# 创建综合评估矩阵
# Create comprehensive evaluation matrix
FOR each recommendation:
impact_score = calculate_business_impact(recommendation, role_insights)
feasibility_score = calculate_technical_feasibility(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)
@@ -117,21 +120,21 @@ END FOR
SORT recommendations BY priority_score DESC
```
## 📊 **输出结构**
## 📊 **Output Specification**
### 保存位置
### Output Location
```
.workflow/WFS-{topic-slug}/.brainstorming/
├── synthesis-report.md # 综合分析报告
├── recommendations-matrix.md # 优先级推荐矩阵
├── action-plan.md # 实施行动计划
├── consensus-analysis.md # 共识和分歧分析
└── brainstorm-summary.json # 机器可读的综合数据
├── synthesis-report.md # Comprehensive synthesis analysis report
├── recommendations-matrix.md # Priority recommendation matrix
├── action-plan.md # Implementation action plan
├── consensus-analysis.md # Consensus and disagreement analysis
└── brainstorm-summary.json # Machine-readable synthesis data
```
### 核心输出文档
### Core Output Documents
#### synthesis-report.md 结构
#### synthesis-report.md Structure
```markdown
# Brainstorming Synthesis Report: {Topic}
*Generated: {timestamp} | Session: WFS-{topic-slug}*
@@ -169,7 +172,7 @@ SORT recommendations BY priority_score DESC
- Innovation potential: {potential_assessment}
2. **{breakthrough_idea_2}**
- Origin: {source_role}
- Origin: {source_role}
- Cross-role support: {supporting_roles}
- Innovation potential: {potential_assessment}
@@ -238,7 +241,7 @@ SORT recommendations BY priority_score DESC
## Next Steps and Follow-up
### Immediate Actions Required
### Decision Points Needing Resolution
### Decision Points Needing Resolution
### Continuous Monitoring Requirements
### Future Brainstorming Sessions Recommended
@@ -246,10 +249,10 @@ SORT recommendations BY priority_score DESC
*This synthesis integrates insights from {role_count} perspectives to provide comprehensive strategic guidance.*
```
## 🔄 **会话集成**
## 🔄 **Session Integration**
### 状态同步
综合分析完成后,更新 `workflow-session.json`:
### Status Synchronization
Upon completion, update `workflow-session.json`:
```json
{
"phases": {
@@ -275,25 +278,32 @@ SORT recommendations BY priority_score DESC
}
```
## ✅ **质量标准**
## ✅ **Quality Assurance**
### 必须包含的综合元素
- [ ] 所有可用角色分析的整合
- [ ] 明确的共识和分歧识别
- [ ] 量化的优先级推荐矩阵
- [ ] 可执行的实施计划
- [ ] 全面的风险评估和缓解
### Required Synthesis Elements
- [ ] Integration of all available role analyses with comprehensive coverage
- [ ] Clear identification of consensus areas and disagreement points
- [ ] Quantified priority recommendation matrix with evaluation criteria
- [ ] Actionable implementation plan with phased approach
- [ ] Comprehensive risk assessment with mitigation strategies
### 综合分析质量检查
- [ ] **完整性**: 整合所有可用的角色分析
- [ ] **洞察力**: 识别跨角色的深层次模式
- [ ] **可操作性**: 提供具体可执行的建议
- [ ] **平衡性**: 考虑所有角色的观点和关切
- [ ] **前瞻性**: 包含长期战略和创新考量
### Synthesis Analysis Quality Standards
- [ ] **Completeness**: Integrates all available role analyses without gaps
- [ ] **Insight Generation**: Identifies cross-role patterns and deep insights
- [ ] **Actionability**: Provides specific, executable recommendations and next steps
- [ ] **Balance**: Considers all role perspectives and addresses concerns
- [ ] **Forward-Looking**: Includes long-term strategic and innovation considerations
### 输出验证标准
- [ ] 推荐优先级基于多维度评估
- [ ] 实施计划考虑资源和时间约束
- [ ] 风险评估全面且有缓解策略
- [ ] 成功指标明确可测量
- [ ] 后续行动清晰具体
### Output Validation Criteria
- [ ] **Priority-Based**: Recommendations prioritized using multi-dimensional evaluation
- [ ] **Resource-Aware**: Implementation plans consider resource and time constraints
- [ ] **Risk-Managed**: Comprehensive risk assessment with mitigation strategies
- [ ] **Measurable Success**: Clear success metrics and monitoring frameworks
- [ ] **Clear Actions**: Specific next steps with assigned responsibilities and timelines
### Integration Excellence Standards
- [ ] **Cross-Role Synthesis**: Successfully identifies and resolves role perspective conflicts
- [ ] **Strategic Coherence**: Recommendations form coherent strategic direction
- [ ] **Implementation Readiness**: Plans are detailed enough for immediate execution
- [ ] **Stakeholder Alignment**: Addresses needs and concerns of all key stakeholders
- [ ] **Continuous Improvement**: Establishes framework for ongoing optimization and learning

View File

@@ -10,51 +10,61 @@ examples:
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🏗️ **角色定义: System Architect**
## 🏗️ **Role Overview: System Architect**
### 核心职责
- **技术架构设计**: 设计可扩展、可维护的系统架构
- **技术选型**: 评估和选择合适的技术栈和工具
- **系统集成**: 设计系统间的集成和通信机制
- **性能优化**: 识别性能瓶颈并提出优化方案
### Role Definition
Technical leader responsible for designing scalable, maintainable, and high-performance system architectures that align with business requirements and industry best practices.
### 关注领域
- **可扩展性**: 系统容量规划、负载处理、弹性扩展
- **可靠性**: 高可用性、容错设计、灾难恢复
- **安全性**: 架构安全、数据保护、访问控制
- **维护性**: 代码质量、模块化设计、技术债务管理
### Core Responsibilities
- **Technical Architecture Design**: Create scalable and maintainable system architectures
- **Technology Selection**: Evaluate and choose appropriate technology stacks and tools
- **System Integration**: Design inter-system communication and integration patterns
- **Performance Optimization**: Identify bottlenecks and propose optimization solutions
## 🧠 **分析框架**
### Focus Areas
- **Scalability**: Capacity planning, load handling, elastic scaling strategies
- **Reliability**: High availability design, fault tolerance, disaster recovery
- **Security**: Architectural security, data protection, access control patterns
- **Maintainability**: Code quality, modular design, technical debt management
### Success Metrics
- System performance benchmarks (latency, throughput)
- Availability and uptime metrics
- Scalability handling capacity growth
- Technical debt and maintenance efficiency
## 🧠 **Analysis Framework**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **架构设计**:
- 当前架构的优势和局限性是什么?
- 如何设计满足业务需求的技术架构?
- 微服务vs单体架构的权衡
### Key Analysis Questions
2. **技术选型**:
- 哪些技术栈最适合当前需求?
- 新技术的引入风险和收益?
- 团队技术能力与选型的匹配度?
**1. Architecture Design Assessment**
- What are the strengths and limitations of current architecture?
- How should we design architecture to meet business requirements?
- What are the trade-offs between microservices vs monolithic approaches?
3. **系统集成**:
- 系统间如何高效集成和通信?
- 第三方服务集成策略?
- API设计和版本管理
**2. Technology Selection Strategy**
- Which technology stack best fits current requirements?
- What are the risks and benefits of introducing new technologies?
- How well does team expertise align with technology choices?
4. **性能和扩展**:
- 系统性能瓶颈在哪里?
- 如何应对流量增长?
- 数据库扩展和优化策略?
**3. System Integration Planning**
- How should systems efficiently integrate and communicate?
- What are the third-party service integration strategies?
- How should we design APIs and manage versioning?
## ⚙️ **执行协议**
**4. Performance and Scalability**
- Where are the current system performance bottlenecks?
- How should we handle traffic growth and scaling demands?
- What database scaling and optimization strategies are needed?
### Phase 1: 会话检测与初始化
## ⚙️ **Execution Protocol**
### Phase 1: Session Detection & Initialization
```bash
# 自动检测活动会话
# Detect active workflow session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
@@ -63,14 +73,14 @@ ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
### Phase 2: Directory Structure Creation
```bash
# 创建系统架构师分析目录
# Create system architect analysis directory
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
```
### Phase 3: TodoWrite 初始化
设置系统架构师视角分析的任务跟踪:
### Phase 3: Task Tracking Initialization
Initialize system architect perspective analysis tracking:
```json
[
{"content": "Initialize system architect brainstorming session", "status": "completed", "activeForm": "Initializing session"},
@@ -83,7 +93,7 @@ mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/system-architect/
]
```
### Phase 4: 概念规划代理协调
### Phase 4: Conceptual Planning Agent Coordination
```bash
Task(conceptual-planning-agent): "
Conduct system architecture perspective brainstorming for: {topic}
@@ -136,26 +146,26 @@ OUTPUT REQUIREMENTS: Save comprehensive analysis to:
Apply system architecture expertise to generate scalable, maintainable, and performant solutions."
```
## 📊 **输出结构**
## 📊 **Output Specification**
### 保存位置
### Output Location
```
.workflow/WFS-{topic-slug}/.brainstorming/system-architect/
├── analysis.md # 主要架构分析
├── architecture-design.md # 详细系统设计和图表
├── technology-stack.md # 技术栈建议和理由
└── integration-plan.md # 系统集成和API策略
├── analysis.md # Primary architecture analysis
├── architecture-design.md # Detailed system design and diagrams
├── technology-stack.md # Technology stack recommendations and justifications
└── integration-plan.md # System integration and API strategies
```
### 文档模板
### Document Templates
#### analysis.md 结构
#### analysis.md Structure
```markdown
# System Architecture Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心架构发现和建议概述]
[Key architectural findings and recommendations overview]
## Current State Assessment
### Existing Architecture Overview
@@ -166,10 +176,10 @@ Apply system architecture expertise to generate scalable, maintainable, and perf
## Requirements Analysis
### Functional Requirements
### Non-Functional Requirements
- Performance: [响应时间、吞吐量要求]
- Scalability: [用户量、数据量增长预期]
- Availability: [可用性要求]
- Security: [安全要求]
- Performance: [Response time, throughput requirements]
- Scalability: [User growth, data volume expectations]
- Availability: [Uptime requirements]
- Security: [Security requirements]
## Proposed Architecture
### High-Level Architecture Design
@@ -190,10 +200,10 @@ Apply system architecture expertise to generate scalable, maintainable, and perf
### Long-term Maintenance Plan
```
## 🔄 **会话集成**
## 🔄 **Session Integration**
### 状态同步
分析完成后,更新 `workflow-session.json`:
### Status Synchronization
Upon completion, update `workflow-session.json`:
```json
{
"phases": {
@@ -209,33 +219,40 @@ Apply system architecture expertise to generate scalable, maintainable, and perf
}
```
### 与其他角色的协作
系统架构师视角为其他角色提供:
- **技术约束和可能性** → Product Manager
- **架构要求和限制** → UI Designer
- **数据架构需求** → Data Architect
- **安全架构框架** → Security Expert
- **技术实现框架** → Feature Planner
### Cross-Role Collaboration
System architect perspective provides:
- **Technical Constraints and Possibilities** → Product Manager
- **Architecture Requirements and Limitations** → UI Designer
- **Data Architecture Requirements** → Data Architect
- **Security Architecture Framework** → Security Expert
- **Technical Implementation Framework** → Feature Planner
## ✅ **质量标准**
## ✅ **Quality Assurance**
### 必须包含的分析元素
- [ ] 清晰的架构图和组件设计
- [ ] 详细的技术栈评估和推荐
- [ ] 可扩展性和性能分析
- [ ] 系统集成和API设计
- [ ] 风险评估和缓解策略
### Required Analysis Elements
- [ ] Clear architecture diagrams and component designs
- [ ] Detailed technology stack evaluation and recommendations
- [ ] Scalability and performance analysis with metrics
- [ ] System integration and API design specifications
- [ ] Comprehensive risk assessment and mitigation strategies
### 架构设计原则检查
- [ ] 可扩展性:系统能够处理增长
- [ ] 可维护性:代码结构清晰,易于修改
- [ ] 可靠性:具有容错和恢复机制
- [ ] 安全性:内置安全控制和保护
- [ ] 性能优化:满足响应时间和吞吐量要求
### Architecture Design Principles
- [ ] **Scalability**: System can handle growth in users and data
- [ ] **Maintainability**: Clear code structure, easy to modify and extend
- [ ] **Reliability**: Built-in fault tolerance and recovery mechanisms
- [ ] **Security**: Integrated security controls and protection measures
- [ ] **Performance**: Meets response time and throughput requirements
### 技术决策验证
- [ ] 技术选型有充分理由和对比分析
- [ ] 架构模式适合业务需求
- [ ] 集成方案考虑了兼容性和维护成本
- [ ] 部署策略可行且风险可控
- [ ] 监控和运维策略完整
### Technical Decision Validation
- [ ] Technology choices have thorough justification and comparison analysis
- [ ] Architectural patterns align with business requirements and constraints
- [ ] Integration solutions consider compatibility and maintenance costs
- [ ] Deployment strategies are feasible with acceptable risk levels
- [ ] Monitoring and operations strategies are comprehensive and actionable
### Implementation Readiness
- [ ] **Technical Feasibility**: All proposed solutions are technically achievable
- [ ] **Resource Planning**: Resource requirements clearly defined and realistic
- [ ] **Risk Management**: Technical risks identified with mitigation plans
- [ ] **Performance Validation**: Architecture can meet performance requirements
- [ ] **Evolution Strategy**: Design allows for future growth and changes

View File

@@ -10,51 +10,61 @@ examples:
allowed-tools: Task(conceptual-planning-agent), TodoWrite(*)
---
## 🎨 **角色定义: UI Designer**
## 🎨 **Role Overview: UI Designer**
### 核心职责
- **用户体验设计**: 创造直观、高效的用户体验
- **界面设计**: 设计美观、功能性的用户界面
- **交互设计**: 设计流畅的用户交互流程
- **可访问性设计**: 确保产品对所有用户友好
### Role Definition
Creative professional responsible for designing intuitive, accessible, and visually appealing user interfaces that create exceptional user experiences aligned with business goals and user needs.
### 关注领域
- **用户体验**: 用户旅程、易用性、满意度、转化率
- **视觉设计**: 界面美学、品牌一致性、视觉层次
- **交互设计**: 操作流程、反馈机制、响应性能
- **可访问性**: WCAG标准、无障碍设计、包容性设计
### Core Responsibilities
- **User Experience Design**: Create intuitive and efficient user experiences
- **Interface Design**: Design beautiful and functional user interfaces
- **Interaction Design**: Design smooth user interaction flows and micro-interactions
- **Accessibility Design**: Ensure products are inclusive and accessible to all users
## 🧠 **分析框架**
### Focus Areas
- **User Experience**: User journeys, usability, satisfaction metrics, conversion optimization
- **Visual Design**: Interface aesthetics, brand consistency, visual hierarchy
- **Interaction Design**: Workflow optimization, feedback mechanisms, responsiveness
- **Accessibility**: WCAG compliance, inclusive design, assistive technology support
### Success Metrics
- User satisfaction scores and usability metrics
- Task completion rates and conversion metrics
- Accessibility compliance scores
- Visual design consistency and brand alignment
## 🧠 **Analysis Framework**
@~/.claude/workflows/brainstorming-principles.md
@~/.claude/workflows/conceptual-planning-agent.md
### 核心分析问题
1. **用户需求和行为**:
- 用户在使用过程中的主要痛点是什么?
- 用户的期望和实际体验之间的差距?
- 不同用户群体的特殊需求?
### Key Analysis Questions
2. **界面和交互设计**:
- 如何简化操作流程?
- 界面信息架构是否合理?
- 交互反馈是否及时和清晰?
**1. User Needs and Behavior Analysis**
- What are the main pain points users experience during interactions?
- What gaps exist between user expectations and actual experience?
- What are the specific needs of different user segments?
3. **视觉和品牌**:
- 视觉设计是否支持品牌形象?
- 颜色、字体、布局的合理性?
- 跨平台一致性如何保证?
**2. Interface and Interaction Design**
- How can we simplify operational workflows?
- Is the information architecture logical and intuitive?
- Are interaction feedback mechanisms timely and clear?
4. **技术和实现**:
- 设计的技术可行性?
- 响应式设计要求?
- 性能对用户体验的影响?
**3. Visual and Brand Strategy**
- Does the visual design support and strengthen brand identity?
- Are color schemes, typography, and layouts appropriate and effective?
- How can we ensure cross-platform consistency?
## ⚙️ **执行协议**
**4. Technical Implementation Considerations**
- What are the technical feasibility constraints for design concepts?
- What responsive design requirements must be addressed?
- How do performance considerations impact user experience?
### Phase 1: 会话检测与初始化
## ⚙️ **Execution Protocol**
### Phase 1: Session Detection & Initialization
```bash
# 自动检测活动会话
# Detect active workflow session
CHECK: .workflow/.active-* marker files
IF active_session EXISTS:
session_id = get_active_session()
@@ -63,14 +73,14 @@ ELSE:
request_user_for_session_creation()
```
### Phase 2: 目录结构创建
### Phase 2: Directory Structure Creation
```bash
# 创建UI设计师分析目录
# Create UI designer analysis directory
mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
```
### Phase 3: TodoWrite 初始化
设置UI设计师视角分析的任务跟踪
### Phase 3: Task Tracking Initialization
Initialize UI designer perspective analysis tracking:
```json
[
{"content": "Initialize UI designer brainstorming session", "status": "completed", "activeForm": "Initializing session"},
@@ -83,7 +93,7 @@ mkdir -p .workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
]
```
### Phase 4: 概念规划代理协调
### Phase 4: Conceptual Planning Agent Coordination
```bash
Task(conceptual-planning-agent): "
Conduct UI designer perspective brainstorming for: {topic}
@@ -142,26 +152,26 @@ OUTPUT REQUIREMENTS: Save comprehensive analysis to:
Apply UI/UX design expertise to create user-centered, accessible, and visually appealing solutions."
```
## 📊 **输出结构**
## 📊 **Output Specification**
### 保存位置
### Output Location
```
.workflow/WFS-{topic-slug}/.brainstorming/ui-designer/
├── analysis.md # 主要UI/UX分析
├── design-system.md # 视觉设计指南和组件
├── user-flows.md # 用户旅程地图和交互流程
└── accessibility-plan.md # 可访问性要求和实现
├── analysis.md # Primary 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
```
### 文档模板
### Document Templates
#### analysis.md 结构
#### analysis.md Structure
```markdown
# UI Designer Analysis: {Topic}
*Generated: {timestamp}*
## Executive Summary
[核心UX发现和设计建议概述]
[Key UX findings and design recommendations overview]
## Current UX Assessment
### User Pain Points
@@ -200,10 +210,10 @@ Apply UI/UX design expertise to create user-centered, accessible, and visually a
### Iteration Framework
```
## 🔄 **会话集成**
## 🔄 **Session Integration**
### 状态同步
分析完成后,更新 `workflow-session.json`:
### Status Synchronization
Upon completion, update `workflow-session.json`:
```json
{
"phases": {
@@ -219,33 +229,40 @@ Apply UI/UX design expertise to create user-centered, accessible, and visually a
}
```
### 与其他角色的协作
UI设计师视角为其他角色提供:
- **用户界面要求** → System Architect
- **用户体验指标** → Product Manager
- **数据展示需求** → Data Architect
- **安全交互设计** → Security Expert
- **功能界面规范** → Feature Planner
### Cross-Role Collaboration
UI designer perspective provides:
- **User Interface Requirements** → System Architect
- **User Experience Metrics and Goals** → Product Manager
- **Data Visualization Requirements** → Data Architect
- **Secure Interaction Design Patterns** → Security Expert
- **Feature Interface Specifications** → Feature Planner
## ✅ **质量标准**
## ✅ **Quality Assurance**
### 必须包含的设计元素
- [ ] 详细的用户旅程分析
- [ ] 完整的界面设计方案
- [ ] 可访问性合规计划
- [ ] 响应式设计策略
- [ ] 可用性测试方案
### Required Design Elements
- [ ] Comprehensive user journey analysis with pain points identified
- [ ] Complete interface design solution with visual mockups
- [ ] Accessibility compliance plan meeting WCAG 2.1 standards
- [ ] Responsive design strategy for multiple devices and screen sizes
- [ ] Usability testing plan with clear success metrics
### 设计原则检查
- [ ] 用户中心:设计以用户需求为核心
- [ ] 一致性:界面元素和交互保持一致
- [ ] 可访问性符合WCAG无障碍标准
- [ ] 可用性:操作简单直观,学习成本低
- [ ] 美观性:视觉设计支持品牌和用户喜好
### Design Principles Validation
- [ ] **User-Centered**: All design decisions prioritize user needs and goals
- [ ] **Consistency**: Interface elements and interactions maintain visual and functional consistency
- [ ] **Accessibility**: Design meets WCAG guidelines and supports assistive technologies
- [ ] **Usability**: Operations are simple, intuitive, with minimal learning curve
- [ ] **Visual Appeal**: Design supports brand identity while creating positive user emotions
### UX评估指标
- [ ] 任务完成率和完成时间
- [ ] 用户满意度和净推荐值
- [ ] 错误率和恢复时间
- [ ] 可访问性合规得分
- [ ] 跨设备一致性评估
### UX Quality Metrics
- [ ] **Task Success**: High task completion rates with minimal errors
- [ ] **Efficiency**: Optimal task completion times with streamlined workflows
- [ ] **Satisfaction**: Positive user feedback and high satisfaction scores
- [ ] **Accessibility**: Full compliance with accessibility standards and inclusive design
- [ ] **Consistency**: Uniform experience across different devices and platforms
### Implementation Readiness
- [ ] **Design System**: Comprehensive component library and style guide
- [ ] **Prototyping**: Interactive prototypes demonstrating key user flows
- [ ] **Documentation**: Clear specifications for development implementation
- [ ] **Testing Plan**: Structured approach for usability and accessibility validation
- [ ] **Iteration Strategy**: Framework for continuous design improvement based on user feedback