gsd-explore

To explore a vague product idea before planning, use Socratic ideation to surface probing questions that clarify goals, assumptions, and constraints. This interactive questioning helps evaluate options and risks early, preventing premature execution and routing outcomes into the correct next phase.

Socratic ideation for engineering requirements uses probing questions to clarify goals, assumptions, and constraints. It guides open-ended exploration of your idea, helping identify risks and priorities through interactive question handling before moving into actual planning or execution phases.

To turn abstract ideas into clear next steps for research workflows, apply open-ended ideation to explore options and surface the right questions early. The process routes outcomes into appropriate artifacts, ensuring your requirements and priorities are defined before execution begins.

This ideation approach implements safe fallback behavior when user input is unavailable, allowing the session to continue. However, it requires interactive question handling to effectively probe goals and constraints, meaning continuous user input significantly improves the quality of the exploration.

The best way to question assumptions during early product design exploration is applying Socratic questioning to clarify goals and constraints. This method surfaces hidden risks and priorities through probing questions, ensuring your design requirements are fully examined before committing to a plan.

You should not use Socratic ideation when you already have clear requirements and defined next steps, as it targets vague ideas needing exploration. If your product or engineering workflow requires immediate execution rather than probing questions, this exploratory approach will add unnecessary overhead.