ywc-brainstorm

Turn rough ideas into validated design specifications by engaging in a Socratic dialogue that decomposes ambiguous requirements and establishes clear success criteria during the pre-planning phase. This structured workflow surfaces project anchors like What, Why, Out of Scope, and Done When to prevent implementation drift.

Prevent implementation drift by enforcing a hard gate that blocks code generation, spec drafting, and implementation until a design is explicitly approved. This ensures wasted effort is minimized by clarifying intent and constraints before development begins.

Socratic dialogue helps with brainstorming by guiding users through a structured 6-step process to surface project anchors. It transforms ambiguous feature requests into validated design specifications by questioning intent, constraints, and success criteria before planning begins.

You can generate visual mockups during design planning by creating divergent HTML mockups for design-heavy requests. This visual exploration captures user taste and reveals Unknown Knowns before production begins, ensuring the final design aligns with user expectations.

Brainstorming blocks code generation by enforcing a strict hard gate that prevents implementation, spec drafting, and code generation until a design is explicitly approved. This gate secures design validation before any development effort starts.

You should not use a Socratic workflow for software design planning when your requirements are already fully validated and unambiguous. This workflow specifically targets the pre-planning phase to decompose complex requirements, so clear specifications do not require the dialogue process.