harness-brainstorm

To clarify intent and constraints before planning, use guided brainstorming to elicit requirements, explore context, and define success criteria. This prevents scope creep by producing a concrete execution spec rather than relying on vague ideas.

The best way to translate vague ideas into an approved execution spec is through a structured brainstorming process that frames the problem, defines scope, and captures constraints. This de-risks planning and ensures alignment before implementation.

To prevent scope creep and drift when handing off execution plans, apply governance guardrails that require saving an approved spec to docs/exec-plans/specs before planning. This enforces traceability and stops premature implementation.

You need requirement elicitation and problem framing for execution planning when starting with ambiguous goals. Defining options and constraints early de-risks handoffs by ensuring the team and AI agents share a concrete understanding of the scope.

Yes, requirement elicitation for planning requires saving the finalized spec to docs/exec-plans/specs. This directory acts as a governance checkpoint, enforcing traceability before prompting a transition to the next planning phase.

Yes, you can use structured brainstorming to define success criteria for governance workflows. It provides a guided process to explore context and requirements, ensuring the resulting execution spec meets all necessary compliance and scope boundaries.