brainstorming

To convert a vague product request into a design specification, use a structured clarifying flow that asks one question at a time to surface constraints, presents 2-3 alternative proposals with trade-offs, and saves the approved design spec to history/<feature>/spec.md.

The best way to gather requirements before feature implementation is to enforce an incremental validation process, presenting design sections for user approval sequentially and avoiding batched questions that hide latent requirements.

Yes, the brainstorming workflow optionally launches a local visual preview runtime to evaluate layout and hierarchy decisions, capturing browser selections directly back into the active design session.

Yes, you need Node.js installed as a dependency to optionally launch the local visual preview runtime and execute the associated scripts during the design specification process.

Finalized design specs are handed off by writing the approved document to history/<feature>/spec.md, running an automated subagent self-review, updating the .pulse/STATE.md file, and transferring context to pulse:exploring without triggering planning or execution.

You should not use an incremental design spec workflow during late-stage implementation or execution phases, as this process is designed strictly for early-stage feature design, architecture decisions, scoping, and evaluation tasks before planning begins.