Our take Editorial verdict
The entry skill is the reason the rest of the methodology works. Brainstorming refuses to let the agent jump into code, classifies how much process a request needs, and drives the idea through context, refinement, a chunked design, and explicit human sign-off before anything is planned or built.
Best for
New features, ambiguous product asks, and any request where the agent would otherwise choose an implementation before the problem is understood.
Keep in mind Limits and tradeoffs
It adds deliberate friction that is wasted on tiny, already-specified changes, and its value depends on the human actually engaging with the design chunks instead of approving them unread.
How to turn an idea into an approved design
- Provide the problem, existing project context and constraints that a design must respect.
- Work through the questions and review the proposed design in manageable sections before implementation.
- Confirm the tradeoffs and acceptance criteria, then hand the approved design to planning.
This is a source-based editorial review. No retained execution or installation test is published here. The starter request is illustrative, not an observed result. Check the setup and compatibility caveats before using it.
Explore Jesse Vincent Superpowers · Skill reference and original instructions
Try this skill
Install · Collection / plugin
Run in Claude Code chat. Installs the whole Superpowers plugin: the methodology, other skills and harness integration. Install separately for each agent. Scope is chosen by the agent plugin manager.
/plugin install superpowers@claude-plugins-official
Command / route checked 30 October 2026. Upstream installation
Setup requirements and caveats
Run in Claude Code chat. Installs the whole Superpowers plugin: the methodology, other skills and harness integration. Install separately for each agent. Scope is chosen by the agent plugin manager.
These are documented requirements; installation has not been tested here.
Your agent needs its own account, runtime and model access. Usage charges depend on your plan; unrecorded costs are unknown.
Run the example
Start a fresh session in the target project. Provide the relevant files or diff. This is the review’s example request, not a record of your execution.
Use the brainstorming skill. Brainstorm a team-invitations feature end to end and show me the design in reviewable chunks before writing a plan or any code.
Check your result · Successful first run
An interactive design proposal shown in reviewable chunks for your approval.
Confirm the agent loaded the named skill, inspect the output and run the relevant checks. Installation alone does not prove a successful run.
Something not working?
The skill is missing from my agent
Check that the skill is installed for the selected agent and project/global scope. Open a fresh session in that project and check the agent’s skill list. Plugin installs may also need to be enabled.
The wrong skill runs, or nothing happens
Start a fresh conversation, explicitly name the skill using the request above, and provide the requested inputs. Ask the agent to confirm which skill it loaded. Check for duplicate installed copies or overlapping instructions.
The skill runs but the result is poor
Compare the result with the successful-first-run check above. Supply the missing files, reproduction steps or constraints, then ask for one focused correction. If the skill addresses a different problem, return to the task guide and compare alternatives.
Installation troubleshooting · missing dependencies
If npx fails, check the Node/npm versions in setup requirements, Git and network access. For skills CLI installs, run npx skills list (add -g for global). If a route changed, follow upstream instructions.
Collection background and tradeoffs
The methodology is deliberately heavy. Brainstorming, chunked design review, and a full written plan add real friction to small or already-clear changes, and the automatic skill-invocation rule can feel rigid. Its richest behavior assumes a harness with subagents, hooks, and a plugin marketplace, so the experience is uneven across agents even though the skills themselves travel well.
Source maintained by Jesse Vincent. Read original skill. Compatibility guidance and published showcase runs remain separate from your first run.
Evidence and provenance Sources and retained files
Evidence and provenance
Review method not recorded. The editorial date does not establish a source inspection or test run.
No executed test recorded. Compatibility guidance and source review do not establish tested behavior.