mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-09 02:24:11 +08:00
docs: 重新组织场景顺序,突出头脑风暴在复杂功能开发中的作用
### 主要改进 **场景顺序优化** - 从简单到复杂的逻辑流程: 1. **场景 1:快速功能开发** - 简单功能的 plan → execute 模式 2. **场景 2:复杂功能的多智能体头脑风暴** - 展示完整工作流:brainstorm → plan → execute 3. **场景 3:UI 设计** - 专业化工作流 4. **场景 4:Bug 修复** - 维护场景 **场景 2 的关键改进**: - 明确头脑风暴应在 plan 之前,用于复杂功能的需求分析 - 展示完整的三阶段工作流(头脑风暴 → 规划 → 执行) - 简化说明,移除冗余的角色列表和阶段详情 - 聚焦于"何时使用头脑风暴"的实用指导 **内容精简**: - 移除重复的专家角色详细列表(从原来的详细分类简化为一句话) - 移除工作流阶段的详细说明(用户可从实际执行中了解) - 更紧凑的场景描述,提高可读性 - 减少 22 行代码(99 → 77 行变更) **逻辑一致性提升**: - 场景 1:适合新手,快速上手 - 场景 2:展示 CCW 最强大的功能 - 多智能体协作 - 场景 3-4:专业化场景,展示多样性 **用户体验改进**: 用户现在可以清楚地理解: 1. 简单功能直接 plan 2. 复杂功能先 brainstorm 再 plan 3. 完整的工作流逻辑顺序 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -82,79 +82,70 @@ Understanding these concepts will help you use CCW more effectively:
|
||||
|
||||
## 🛠️ Common Scenarios
|
||||
|
||||
### Scenario 1: Developing a New Feature (as shown above)
|
||||
### Scenario 1: Quick Feature Development
|
||||
|
||||
This is the most common use case, following the "start session → plan → execute" pattern.
|
||||
For simple, well-defined features, use the direct "plan → execute" pattern:
|
||||
|
||||
```bash
|
||||
# 1. Start a session
|
||||
/workflow:session:start "User Login Feature"
|
||||
|
||||
# 2. Create a plan
|
||||
# Create plan (auto-creates session)
|
||||
/workflow:plan "Implement JWT-based user login and registration"
|
||||
|
||||
# 3. Execute
|
||||
# Execute
|
||||
/workflow:execute
|
||||
```
|
||||
|
||||
### Scenario 2: UI Design
|
||||
> **💡 Note**: `/workflow:plan` automatically creates a session. You can also manually start a session first with `/workflow:session:start "Feature Name"`.
|
||||
|
||||
CCW has powerful UI design capabilities, capable of generating complex UI prototypes from simple text descriptions.
|
||||
### Scenario 2: Complex Feature with Multi-Agent Brainstorming
|
||||
|
||||
For complex features requiring thorough analysis, use the complete workflow: **brainstorm → plan → execute**
|
||||
|
||||
```bash
|
||||
# 1. Start a UI design workflow
|
||||
/workflow:ui-design:explore-auto --prompt "A modern, clean admin dashboard login page with username, password fields and a login button"
|
||||
|
||||
# 2. View the generated prototype
|
||||
# After the command finishes, it will provide a path to a compare.html file. Open it in your browser to preview.
|
||||
```
|
||||
|
||||
### Scenario 3: Fixing a Bug
|
||||
|
||||
CCW can help you analyze and fix bugs.
|
||||
|
||||
```bash
|
||||
# 1. Use the bug-index command to analyze the problem
|
||||
/cli:mode:bug-index "Incorrect success message even with wrong password on login"
|
||||
|
||||
# 2. The AI will analyze the relevant code and generate a fix plan. You can then execute this plan.
|
||||
/workflow:execute
|
||||
```
|
||||
|
||||
### Scenario 4: Multi-Agent Brainstorming
|
||||
|
||||
Before implementing complex features, use multi-agent brainstorming to explore different perspectives and generate comprehensive specifications.
|
||||
|
||||
```bash
|
||||
# Automatic role selection and parallel analysis (auto-creates session)
|
||||
# Step 1: Multi-agent brainstorming (auto-creates session)
|
||||
/workflow:brainstorm:auto-parallel "Design a real-time collaborative document editing system with conflict resolution"
|
||||
|
||||
# Specify number of expert roles (default: 3, max: 9)
|
||||
# Optional: Specify number of expert roles (default: 3, max: 9)
|
||||
/workflow:brainstorm:auto-parallel "Build scalable microservices platform" --count 5
|
||||
|
||||
# Step 2: Generate implementation plan from brainstorming results
|
||||
/workflow:plan
|
||||
|
||||
# Step 3: Execute the plan
|
||||
/workflow:execute
|
||||
```
|
||||
|
||||
**How It Works**:
|
||||
- **Auto role selection**: Analyzes your topic and selects relevant expert roles
|
||||
**Brainstorming Benefits**:
|
||||
- **Auto role selection**: Analyzes your topic and selects 3-9 relevant expert roles (system-architect, ui-designer, product-manager, etc.)
|
||||
- **Parallel execution**: Multiple AI agents analyze simultaneously from different perspectives
|
||||
- **Comprehensive output**: Generates integrated specification with cross-role insights
|
||||
- **Comprehensive specification**: Generates integrated requirements and design document
|
||||
|
||||
**Available Expert Roles**:
|
||||
- Technical: `system-architect`, `data-architect`, `subject-matter-expert`
|
||||
- Product & Design: `ui-designer`, `ux-expert`, `product-manager`, `product-owner`
|
||||
- Agile & Quality: `scrum-master`, `test-strategist`
|
||||
- API Design: `api-designer`
|
||||
|
||||
**Workflow Phases**:
|
||||
1. **Framework Generation**: Creates structured discussion framework
|
||||
2. **Parallel Analysis**: Multiple experts analyze simultaneously
|
||||
3. **Synthesis**: Integrates all perspectives into comprehensive specification
|
||||
4. **Action Planning**: Use `/workflow:plan` to generate implementation tasks
|
||||
|
||||
**When to Use**:
|
||||
**When to Use Brainstorming**:
|
||||
- Complex features requiring multiple perspectives
|
||||
- Architectural decisions with significant impact
|
||||
- New product features needing comprehensive analysis
|
||||
- When you want thorough requirements and design specifications
|
||||
- When you need thorough requirements before implementation
|
||||
|
||||
### Scenario 3: UI Design
|
||||
|
||||
CCW has powerful UI design capabilities for generating prototypes from text descriptions:
|
||||
|
||||
```bash
|
||||
# Generate UI design variations (auto-creates session)
|
||||
/workflow:ui-design:explore-auto --prompt "A modern, clean admin dashboard login page"
|
||||
```
|
||||
|
||||
After completion, open the generated `compare.html` file in your browser to preview designs.
|
||||
|
||||
### Scenario 4: Bug Fixing
|
||||
|
||||
Quick bug analysis and fix workflow:
|
||||
|
||||
```bash
|
||||
# Analyze the bug
|
||||
/cli:mode:bug-index "Incorrect success message with wrong password"
|
||||
|
||||
# Generate and execute fix plan
|
||||
/workflow:execute
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user