Brainstorming
Turn a feature request into a clearer problem, chosen approach, and reviewable design.
npx skills add obra/superpowers --skill brainstorming What it does
An implementation can be technically sound while solving the wrong problem. This skill helps the agent investigate the existing context and clarify consequential decisions before committing to a design.
What changes after install
- Reads existing project context before asking questions already answered by the repository.
- Explores approaches and records decisions in a design document.
- Connects an agreed design to a subsequent implementation plan.
Install
Run this command with Node.js 22.20 or later and select your agent in the Skills CLI.
npx skills add obra/superpowers --skill brainstorming Before using Brainstorming
- Provide the feature request and project context, with access to existing files and documentation. Resolve the design with the user before moving to implementation.
Read the reviewed setup instructions for the selected workflow.
When to use it
- Clarifying a feature whose user flow or tradeoffs are still unsettled.
- Comparing implementation approaches before a substantial change.
When not to use it
- Adding a lengthy discovery process to a fully specified, trivial edit.
A request that benefits from clarification
Suppose you want to add saved searches to an existing application. Before implementation, the agent needs to understand who saves them, whether they are private or shared, and what should happen when the underlying data changes. Give it the existing search code, product constraints, and examples of the intended user flow. The skill encourages reading this context first instead of making you repeat information already present.
The source distinguishes an obvious small edit from a request with meaningful open decisions. For the latter, it explores concrete approaches, explains their tradeoffs, and turns the chosen direction into a design that can be reviewed. This is useful when an early product decision would otherwise become an accidental code decision.
What a useful result contains
Look for a description of the user problem, the chosen behavior, boundaries, and the decisions that matter to implementation. The design should be specific enough for you to recognize the result you would get. Unresolved questions should concern meaningful choices rather than routine process details.
The upstream workflow refers to Writing Plans as a next step. Installing this one skill does not necessarily install its companions, so inspect the broader Superpowers setup if you want the complete sequence.
When to keep the process lighter
A precise color change, typo fix, or already approved small adjustment may not need an extended discussion. Your existing instructions and decisions remain important context. This entry describes the source workflow, not a guarantee of better product outcomes. SkillDex has not run a design session to evaluate it.
Related workflows
FAQ
- Does Brainstorming build the feature?
- Its main output is a clarified and reviewed design. The source hands implementation planning to a companion skill.
- Is it only for software?
- No. The upstream description also includes other creative planning tasks, although the surrounding Superpowers workflow is oriented toward agent-assisted development.