brainstorming

Structured ideation turns project ideas into validated design concepts by assessing project context, prompting clarifying questions, proposing multiple options with tradeoffs, and enforcing hard approval gates before any implementation begins.

Document design decisions by generating a formal specification markdown file at docs/superpowers/specs/ to capture validated concepts, then enforce hard approval gates before transitioning to any implementation planning workflow.

Requirement elicitation works by assessing project files, recent commits, and existing docs to discover context, then coordinating ideation to clarify user intent before building features or modifying project behavior.

Yes, structured brainstorming evaluates multiple solution options by proposing design alternatives, mapping their specific tradeoffs, and presenting a clear plan to guide project-wide design exploration and formal approval.

Transition from design exploration to implementation planning by generating a formal design document and handing it off to a dedicated writing-plans workflow that manages downstream execution after design approval.

Do not skip the ideation phase when embarking on creative tasks, because understanding context, user intent, and requirements first prevents misaligned features and ensures formal documentation exists before implementation.