ce:brainstorm

You clarify requirements for ambiguous feature ideas through structured, single-question collaborative dialogue that surfaces relevant context, tests the problem frame, and captures concrete constraints before planning begins.

Brainstorming product scope before planning involves challenging the initial framing, weighing outcomes, and documenting scope boundaries and success criteria in a lightweight requirements document to prevent planning from inventing product behavior.

Structure a collaborative brainstorming session by asking one focused question at a time, preferring single-select choices to guide discovery, and noting opportunities to simplify or defer work before committing to a requirement.

Yes, you can apply this approach when exploring options or reframing ambition, as it pressure-tests the problem framing and produces a durable requirements document with success criteria to decide what should be built.

A requirements document for feature planning should include the problem frame, concrete requirements, scope boundaries, and success criteria so that downstream planning can focus strictly on implementation.

You should avoid structured brainstorming for feature ideation when the requirements are already concrete and unambiguous, as the guided discovery process is specifically designed to resolve vagueness and undecided problems before planning.