Back to Details

development-brainstorming

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Development Brainstorming: Ideas Into Technical Designs

开发头脑风暴：从想法到技术设计

Overview

概述

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design in small sections (200-300 words), checking after each section whether it looks right so far.
通过自然的协作对话，帮助将想法转化为完整成熟的设计和规格说明。
首先了解当前项目背景，然后逐个提出问题来完善想法。当你明确要构建的内容后，将设计拆分为小章节（200-300字）呈现，每完成一个章节后确认目前的内容是否正确。

The Process

流程

Understanding the idea:
  • Check out the current project state first (files, docs, recent commits)
  • Ask questions one at a time to refine the idea
  • Prefer multiple choice questions when possible, but open-ended is fine too
  • Only one question per message - if a topic needs more exploration, break it into multiple questions
  • Focus on understanding: purpose, constraints, success criteria
Exploring approaches:
  • Propose 2-3 different approaches with trade-offs
  • Present options conversationally with your recommendation and reasoning
  • Lead with your recommended option and explain why
Presenting the design:
  • Once you believe you understand what you're building, present the design
  • Break it into sections of 200-300 words
  • Ask after each section whether it looks right so far
  • Cover: architecture, components, data flow, error handling, testing
  • Be ready to go back and clarify if something doesn't make sense
理解想法：
  • 首先查看当前项目状态（文件、文档、近期commit）
  • 逐个提出问题来完善想法
  • 尽可能优先使用选择题，但开放式问题也可
  • 每条消息仅包含一个问题——若某个主题需要深入探讨，拆分为多个问题
  • 聚焦于理解：目标、约束条件、成功标准
探索实现方案：
  • 提出2-3种不同的实现方案，并说明各自的利弊
  • 以对话形式呈现选项，同时给出你的推荐方案及理由
  • 先介绍推荐方案，再解释原因
呈现设计：
  • 当你明确要构建的内容后，开始呈现设计
  • 将设计拆分为200-300字的小章节
  • 每完成一个章节后询问目前内容是否正确
  • 涵盖：架构、组件、数据流、错误处理、测试
  • 若有内容不清晰，随时准备回溯澄清

After the Design

设计完成后

Documentation:
  • Write the validated design to 
    docs/plans/YYYY-MM-DD-<topic>-design.md
  • Use elements-of-style:writing-clearly-and-concisely skill if available
  • Commit the design document to git
Implementation (if continuing):
  • Ask: "Ready to set up for implementation?"
  • Use superpowers:using-git-worktrees to create isolated workspace
  • Use superpowers:writing-plans to create detailed implementation plan
文档记录：
  • 将经过验证的设计写入
    docs/plans/YYYY-MM-DD-<topic>-design.md
  • 若有可用的elements-of-style:writing-clearly-and-concisely技能，可使用该技能
  • 将设计文档commit到git
实现阶段（若继续推进）：
  • 询问："是否准备好进入实现阶段？"
  • 使用superpowers:using-git-worktrees创建独立工作区
  • 使用superpowers:writing-plans制定详细的实现计划

Key Principles

核心原则

  • One question at a time - Don't overwhelm with multiple questions
  • Multiple choice preferred - Easier to answer than open-ended when possible
  • YAGNI ruthlessly - Remove unnecessary features from all designs
  • Explore alternatives - Always propose 2-3 approaches before settling
  • Incremental validation - Present design in sections, validate each
  • Be flexible - Go back and clarify when something doesn't make sense
  • 一次一个问题——不要用多个问题给对方造成负担
  • 优先选择题——可能的话，选择题比开放式问题更易回答
  • 严格遵循YAGNI原则——从所有设计中移除不必要的功能
  • 探索备选方案——确定方案前，始终提出2-3种实现思路
  • 渐进式验证——分章节呈现设计，逐一验证
  • 保持灵活——若有内容不清晰，随时回溯澄清