gsd-explore

To turn a vague software idea into actionable requirements, use structured Socratic ideation to probe assumptions, goals, and constraints, then route the clarified outputs into specific artifacts like requirements and research questions.

Socratic ideation for product discovery is a structured questioning process that clarifies early-stage planning uncertainty. It probes risks and constraints to transform rough concepts into clear directions before committing to execution plans.

Routing exploration outputs into workflow execution artifacts involves converting clarified ideas into structured deliverables. The process directs outputs into notes, todos, seeds, research questions, requirements, or new project phases.

You need to spawn research questions during early-stage planning when Socratic probing identifies critical knowledge gaps. It generates follow-up research prompts to resolve uncertainty before finalizing product requirements.

Yes, you can use structured ideation for a rough authentication strategy concept. It applies Socratic questioning to clarify the approach and routes the outputs into requirements, next-phase work, and supporting research prompts.

The limitation of Socratic ideation for software planning is that it focuses solely on resolving early-stage uncertainty and routing artifacts. It requires a subsequent end-to-end execution flow to implement the generated requirements and research prompts.