groove-work-brainstorm

To clarify project scope, you engage in a guided dialogue that surfaces critical decisions and open questions. This process ensures alignment and identifies potential roadblocks by documenting key decisions and outstanding questions before proceeding to the planning phase.

Documenting brainstorm sessions involves using a predefined template to record requirements, boundaries, and objectives. This structured approach ensures everyone understands the scope and captures any ambiguities or key decisions made during the clarifying dialogue.

Yes, a task backend is required to output and store the documented brainstorm sessions. This integration allows the skill to automatically log key decisions and open questions directly into your existing project management workflow.

You should use guided dialogue during the initial phase of any new feature or project. It helps discuss requirements with an AI to ensure alignment, define what needs to be built, and identify potential roadblocks before writing code.

Scope clarification focuses on defining boundaries and surfacing open questions through dialogue, whereas general planning proceeds afterward. This pre-planning step targets requirement alignment and ambiguity resolution, ensuring the planning phase starts with a clearly defined objective.