brainstorming

To turn ideas into designs and specs, you can use a guided collaborative dialogue process that explores project context, proposes multiple approaches with trade-offs, and generates a committed design doc.

The best way to structure brainstorming for unclear requirements is following a structured discovery process: explore context, ask clarifying questions one at a time, propose 2-3 approaches, and present a recommended design for approval.

To write and save a design doc after brainstorming, the generated spec is saved directly to docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md and committed to your repository for future reference.

Yes, you can transition directly from design brainstorming to implementation planning by invoking the writing-plans skill, which takes your approved design and creates a structured implementation plan.

Collaborative ideation works for early-stage product, feature, and system design tasks, specifically supporting scenarios where requirements are unclear or exploring multiple directions is valuable.