Brainstorming is the Superpowers skill that runs before any creative work. It checks what the agent already knows about your request, asks one question at a time about the biggest open point, and lays out the approaches in a message of their own. Once you pick one, it writes a design document and waits for your approval before the planning skill takes over. Small, clear requests are done directly. Larger projects get a written design that a fresh subagent reads first, so its questions reach you in one round.
What You Get
- A short opening message that plays back your request and what the agent found in the project
- Approaches laid out with trade-offs and a recommendation, for you to pick from
- A design doc saved under docs/superpowers/specs and committed to the repository
- A builder check by a fresh subagent that surfaces questions before you read the doc
- An optional browser tab for mockups and diagrams
Common Use Cases
- Starting a new feature in an existing codebase
- Planning a project from a one-line idea
- Shaping a talk, a business or a renovation, since the skill covers work outside software
- Turning a spec or handoff into a design you have agreed to
What Makes It Unique
Most planning skills jump to a task list. This one spends its effort on the why behind a request, asks one question at a time, and makes approval of a written design a gate. It scales the document to the size of the work and sends it to a fresh subagent that plays the builder before you read it.
Under The Hood
The skill is mostly instructions loaded into the agent’s context, plus a builder-check prompt file and a visual companion. The visual companion starts a small local Node server through shell scripts and serves mockup pages to a browser tab, and a stop script shuts it down. The server creates a random session token, can keep it in an owner-only token file, and requires it before it serves the pages or accepts a socket connection. It writes mockup and event files to disk and can open your browser only when you opt in with an environment variable. The agent writes the design doc into the repository and, with a subagent tool, dispatches a reviewer. The companion page loads the project’s logo from its website with the version number, unless an environment variable turns that off.