Brainstorming
协作类
Must be used before any creative work — creating features, building components, adding capabilities, or modifying behaviors.
Quick Start
Understand in 30 Seconds
Understand requirements through Socratic dialogue, form complete design documentation before implementation.
When to Use
- Starting new feature development
- When requirements are unclear
- Before architecture decisions
Quick Example
User: Help me build a user authentication system
AI: I'm using the brainstorming skill to understand your requirements.
- What login methods should this authentication system support?
- Username/password
- Social login (GitHub/Google)
- Both
Complete Guide
Core Principle
Core Principle: Before presenting a design and getting user approval, you must not call any implementation skills, write any code, scaffold any project, or take any implementation actions.
Anti-pattern: "This is too simple to need design"
Every project goes through this process. A todo list, a single-feature tool, a configuration change — no exceptions.
Checklist
- Explore Project Context — Check files, documentation, recent commits
- Ask Clarifying Questions — One at a time, understand purpose/constraints/success criteria
- Propose 2-3 Options — Include tradeoffs and recommendation
- Present Design — Scale sections by complexity, get user approval after each section
- Write Design Document — Save to
docs/superpowers/specs/YYYY-MM-DD-<topic>-design.mdand commit - Transition to Implementation — Call writing-plans skill to create implementation plan
Key Principles
- One Question at a Time — Don't overwhelm users with multiple questions
- Prefer Multiple Choice — Easier to answer than open-ended
- Ruthless YAGNI — Remove unnecessary features from all designs
- Explore Alternatives — Always propose 2-3 options before deciding
- Incremental Validation — Present design, get approval before continuing
Related Skills
Follow-up Skills
- writing-plans - Write implementation plans
Related Skills
- using-superpowers - Getting started with Superpowers