brainstorming

Structured design dialogue that validates ideas before implementation begins.

obra ↓ 291k
Claude Code
View source ↗

What it does

  • Check out the current project state first (files, docs, recent commits)
  • For appropriately-scoped projects, 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
  • Propose 2-3 different approaches with trade-offs
  • Present options conversationally with your recommendation and reasoning

Requirements & configuration

  • Anti-Pattern: "This Is Too Simple To Need A Design"
  • Only one question per message - if a topic needs more exploration, break it into multiple questions
  • Can someone understand what a unit does without reading its internals? Can you change the internals without breaking consumers? If not, the boundaries need work.
  • 3. Scope check: Is this focused enough for a single implementation plan, or does it need decomposition?
  • Fix any issues inline. No need to re-review — just fix and move on.

Derived from the skill's own SKILL.md documentation · extracted 2026-07-23

Structured design dialogue that validates ideas before implementation begins.

Source

Repository: https://github.com/obra/superpowers

brainstorming FAQ

What does the brainstorming skill do?

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. Check out the current project state first (files, docs, recent commits) For appropriately-scoped projects, ask questions one at a time to refine the idea

What does brainstorming require?

Anti-Pattern: "This Is Too Simple To Need A Design" Only one question per message - if a topic needs more exploration, break it into multiple questions Can someone understand what a unit does without reading its internals? Can you change the internals without breaking consumers? If not, the boundaries need work. 3. Scope check: Is this focused enough for a single implementation plan, or does it need decomposition? Fix any issues inline. No need to re-review — just fix and move on.

How do I install brainstorming?

Run: npx -y skills add https://github.com/obra/superpowers --skill brainstorming --agent claude-code — the source lives at github.com/obra/superpowers.

Maintain brainstorming?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

brainstorming on getagentictools
[![brainstorming on getagentictools](https://getagentictools.com/badge/skills/obra-superpowers-brainstorming.svg)](https://getagentictools.com/skills/obra-superpowers-brainstorming?ref=badge)
npx agentictools info skills/obra-superpowers-brainstorming

The second line is the CLI lookup for this page — handy in READMEs and docs.