ce-brainstorm

To clarify requirements before planning, use collaborative brainstorming to facilitate structured dialogue that surfaces assumptions, aligns on goals, and produces a durable requirements document for implementation handoff.

Defining project scope through collaborative brainstorming involves exploring multiple solution paths and articulating user needs and success criteria, resulting in a balanced scope and artifact-first guidance before committing to a plan.

Explore solution options before deciding what to build by triggering a brainstorming workflow with your feature idea, which prompts option-rich dialogue to think through alternatives and defer premature design decisions.

Yes, you can use brainstorming dialogue to produce a requirements document, as the process enforces a frontmatter-driven metadata contract and outputs durable decisions alongside planning guidance for your team.

You should not use collaborative brainstorming when implementation specifics are already defined, as the process deliberately defers implementation details to the planning phase and focuses solely on scope and requirements gathering.

No, the brainstorming workflow requires no specific dependencies or components to run, allowing you to start immediately by stating the feature idea or problem to explore to trigger the session.