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.
- Kind
- Skill
- Works with
- Claude Code, Codex, Cursor, Gemini / Antigravity
- Source
- obra/superpowers @ 8ca22dba9a94
- Path
- skills/brainstorming/SKILL.md
- License
- MIT
- Jobs
- Requirements interviews, Planning
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs and specs through natural collaborative dialogue. Start by classifying how much process the request needs, then work through your path: understand the context, refine the idea, present a design, and get your human partner's approval. ## Establish Shared Understanding The outcome of brainstorming is an understanding your human partner can recognize and correct, grounded in what they want to accomplish. 1. **Discover intent.** Use the request and available context to identify the intended outcome, who it is for, and what success looks like. When that information is missing, ask one focused question about purpose or intended use before proposing features or an approach. Knowing the app genre does not tell you why your partner wants it. Gathering missing requirements does not ask them to authorize the task again. 2. **Write back your understanding.** Summarize the intended outcome, relevant constraints, and success criteria in a short note your partner can assess. Separate what they said from assumptions. Invite correction …