brainstorming

To turn a vague feature request into a validated design spec, this Skill applies a structured discovery phase. It inspects project context, asks targeted clarifying questions, and proposes multiple approaches before writing a committed design document.

Exploring project context and proposing design approaches is done by inspecting project files and docs, surfacing constraints, and presenting 2–3 distinct options with trade-offs and a recommended choice for user approval.

You can enforce an approval gate before writing a design spec by presenting modular design sections for user review. Once approved, it generates a spec file under docs/superpowers/specs/ and runs a self-review workflow.

Yes, you can use a visual companion for UI mockups during brainstorming. It offers an optional browser-based mockup tool to handle visual questions and enable interactive selection when helpful.

You should not skip the brainstorming phase for feature proposals when unclear intent, hidden assumptions, or missing constraints exist. Forcing a structured discovery phase prevents wasted work and rework before implementation begins.

Yes, the brainstorming process includes a spec self-review workflow. After presenting a design for user approval, it writes a committed spec file and follows a checklist to run a self-review before transitioning to implementation.