brainstorming

To turn informal ideas into validated design specifications, use a structured discovery flow that asks clarifying questions one at a time about purpose, constraints, and success criteria, then proposes 2-3 approaches with trade-offs before writing a final spec.

The best way to brainstorm UI/UX planning requirements is applying a discovery-first approach that decomposes oversized requests, compares design approaches, and secures user approval before any implementation begins, preventing misaligned outcomes and wasted work.

Yes, you can get a visual companion mockup during the spec-writing process. The skill offers an opt-in browser-based mockup and diagram helper to assist with visual questions during the design discovery phase.

To write and save approved design specs, present incremental design sections to obtain user approval, run a spec self-review, and commit the validated spec file directly to the docs/superpowers/specs/ directory.

You should not use a structured discovery approach when a small change requires no clarifying intent, constraints, or success criteria, as the enforced questioning and approach comparison would add unnecessary overhead to trivial tasks.

Yes, the brainstorming skill transitions to writing-plans immediately after spec approval. It enforces a validated spec output and completes a self-review before handing off to the implementation planning phase.