brainstorming

name	brainstorming
description	You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
trigger	when_needed
language	zh-TW
adapted_from	openskills/brainstorming
version	1.0.0-antigravity
original_license	Unknown

BRAINSTORMING 處理指南

技能版本: v1.0 (Antigravity 適配版)
原始來源: openskills/brainstorming
語言: 繁體中文

概述

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

---

Brainstorming Ideas Into Designs

使用情境

此技能適用於以下情況：

• 用戶明確要求相關功能時
• 任務需要專業領域知識時
• 需要遵循特定工作流程時

---

概述

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.

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

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

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

---

專案整合

此技能已適配 Antigravity 系統：

• 遵循 skills/_base/coding_style.md 編碼規範
• 與 skills/_base/architecture.md 架構模式一致
• 符合 Constitution v3.1 語言規範 (繁體中文)

相關技能

可搭配以下技能使用：

• systematic-debugging - 系統化除錯
• verification-before-completion - 完成前驗證