brainstorming

To turn a feature idea into a PRD, the brainstorming process uses structured questioning and approach comparison to refine intent, then authors a validated design specification before any implementation starts.

The best way to validate design specifications is through a hard approval gate that requires user review of a written PRD, ensuring the proposed approach aligns with success criteria before transitioning to planning.

Yes, you can compare multiple design approaches. The brainstorming process presents 2–3 options with specific trade-offs for your feature requirement, then converges on a single recommendation for the specification.

To structure brainstorming for architecture and component behavior changes, the process checks existing project files, asks focused questions to refine intent, and writes a PRD to ground the design validation in reality.

Yes, the design specification process requires a hard user approval gate. A deterministic self-review of the spec is run, and the process only transitions to writing implementation plans after final user review.

You should not use a structured brainstorming approach when implementation has already started or when the creative work does not require a formal PRD, design validation, or a hard approval gate before execution.