brainstorm

Collaborative brainstorming clarifies project requirements through structured dialogue and batched questions before planning execution. You research the idea and capture decisions directly into a design document for later use.

Capturing design documents from feature discussions involves adaptive exit and document capture during brainstorming. This process records your decisions into a reusable blueprint ready for implementation handoff.

Yes, you can use batched questions to explore codebase research and understand what to build. This approach systematically clarifies needs and prepares the context for implementation.

Guided brainstorming produces a reusable blueprint that loads into agent context. This blueprint guides subsequent prompts, parses responses, and generates relevant follow-up questions automatically.

You should avoid using a brainstorming session for requirements gathering when you already have a finalized design document. The process targets clarifying unknown needs rather than executing an established implementation plan.

To start brainstorming a new feature idea, describe your concept using the trigger command followed by the description. This initiates a guided session to clarify requirements and capture decisions.