openspec-explore

To explore ideas and frame problems, you need a thinking partner that guides exploratory reasoning, surfaces risks, and clarifies requirements through prompts and visual aids. This approach helps you investigate problems deeply before or during a change.

The best way to clarify requirements during early discovery is using an exploration mode that acts as a thinking partner, offering option evaluation and problem framing to refine your design scoping and surface hidden risks.

Yes, you can use a thinking partner to visualize thoughts with ASCII visual aids and prompts, effectively surfacing questions and risks while investigating problems across diverse domains.

No, this exploration mode enforces an exploration-only stance and strictly avoids code execution or implementation tasks, focusing entirely on exploratory reasoning and problem framing.

To start evaluating options for design scoping, describe your problem or goal and enter explore mode to begin thinking. The thinking partner will then guide you through option evaluation and requirement refinement.

You should not use an exploratory reasoning approach when you need actual code execution, system implementation, or concrete technical tasks rather than problem framing, risk surfacing, and requirement clarification.