Back to Details

brainstorming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brainstorming Ideas Into Designs

将头脑风暴想法转化为设计

Overview

概述

Transform rough ideas into fully-formed designs through structured questioning and alternative exploration.
Core principle: Ask questions to understand, explore alternatives, present design incrementally for validation.
Announce at start: "I'm using the Brainstorming skill to refine your idea into a design."
通过结构化提问和替代方案探索，将粗略想法转化为完整成熟的设计。
核心原则： 通过提问来理解需求、探索替代方案，逐步呈现设计以获取验证。
开始时告知： "我正在使用头脑风暴技能将你的想法打磨为设计。"

The Process

流程

Phase 1: Understanding

阶段1：理解需求

  • Check current project state in working directory
  • Ask ONE question at a time to refine the idea
  • Prefer multiple choice when possible
  • Gather: Purpose, constraints, success criteria
  • 检查工作目录中的当前项目状态
  • 每次提出一个问题来细化想法
  • 尽可能采用选择题形式
  • 收集信息：目标、约束条件、成功标准

Phase 2: Exploration

阶段2：方案探索

  • Propose 2-3 different approaches
  • For each: Core architecture, trade-offs, complexity assessment
  • Ask your human partner which approach resonates
  • 提出2-3种不同的方法
  • 针对每种方法：核心架构、权衡利弊、复杂度评估
  • 询问协作对象哪种方法更符合需求

Phase 3: Design Presentation

阶段3：设计展示

  • Present in 200-300 word sections
  • Cover: Architecture, components, data flow, error handling, testing
  • Ask after each section: "Does this look right so far?"
  • 以200-300字的分段形式呈现
  • 涵盖内容：架构、组件、数据流、错误处理、测试
  • 每段结束后询问："目前看来这样是否合适？"

Phase 4: Worktree Setup (for implementation)

阶段4：工作区设置（用于实施）

When design is approved and implementation will follow:
  • Announce: "I'm using the Using Git Worktrees skill to set up an isolated workspace."
  • Switch to skills/collaboration/using-git-worktrees
  • Follow that skill's process for directory selection, safety verification, and setup
  • Return here when worktree ready
当设计获得批准且即将开始实施时：
  • 告知："我正在使用Using Git Worktrees技能来设置独立工作区。"
  • 切换至skills/collaboration/using-git-worktrees
  • 遵循该技能的流程进行目录选择、安全验证和设置
  • 工作区准备就绪后返回此处

Phase 5: Planning Handoff

阶段5：计划交接

Ask: "Ready to create the implementation plan?"
When your human partner confirms (any affirmative response):
  • Announce: "I'm using the Writing Plans skill to create the implementation plan."
  • Switch to skills/collaboration/writing-plans skill
  • Create detailed plan in the worktree
询问："是否准备好创建实施计划？"
当协作对象确认（任何肯定回复）时：
  • 告知："我正在使用Writing Plans技能来创建实施计划。"
  • 切换至skills/collaboration/writing-plans技能
  • 在工作区中创建详细计划

When to Revisit Earlier Phases

何时回溯至前期阶段

Go backward when:
  • Partner reveals new constraint during Phase 2 or 3 → Return to Phase 1 to understand it
  • Validation shows fundamental gap in requirements → Return to Phase 1
  • Partner questions approach during Phase 3 → Return to Phase 2 to explore alternatives
  • Something doesn't make sense → Go back and clarify
Don't force forward linearly when going backward gives better results.
需要回溯的情况：
  • 协作对象在阶段2或3中透露新的约束条件 → 返回阶段1以理解该约束
  • 验证显示需求存在根本性缺口 → 返回阶段1
  • 协作对象在阶段3中对方法提出疑问 → 返回阶段2探索替代方案
  • 出现无法理解的内容 → 返回并澄清
不要强行线性推进，回溯能带来更好的结果时应选择回溯。

Related Skills

相关技能

During exploration:
  • When approaches have genuine trade-offs: skills/architecture/preserving-productive-tensions
Before proposing changes to existing code:
  • Understand why it exists: skills/research/tracing-knowledge-lineages
探索阶段：
  • 当方法存在真正的权衡时：skills/architecture/preserving-productive-tensions
在提议修改现有代码之前：
  • 理解代码存在的原因：skills/research/tracing-knowledge-lineages

Remember

注意事项

  • One question per message during Phase 1
  • Apply YAGNI ruthlessly
  • Explore 2-3 alternatives before settling
  • Present incrementally, validate as you go
  • Go backward when needed - flexibility > rigid progression
  • Announce skill usage at start
  • 阶段1中每条消息仅包含一个问题
  • 严格应用YAGNI原则
  • 在确定方案前探索2-3种替代方案
  • 逐步呈现设计，边推进边验证
  • 必要时回溯——灵活性优于僵化的流程
  • 开始时告知所使用的技能