openspec-explore

To explore and refine requirements without writing code, use a guided thinking partner that surfaces clarifying questions, hypotheses, and potential directions. This approach focuses on problem framing and ideation across codebases, strictly avoiding implementation while you visualize freely.

The best way to frame a complex problem space during ideation is by using a conversational exploration tool that surfaces risks, unknowns, and multiple angles. This method helps visualize dependencies and suggests investigations to guide decision-making without prescribing implementations.

Yes, you can use exploration mode to create OpenSpec proposals, designs, and specs. Capturing your thinking in these artifacts is permitted because it represents refining requirements and problem framing, whereas writing actual code or implementing features is strictly prohibited.

Guided problem exploration helps with visualizing dependencies by surfacing interesting threads and diagrams to guide decision-making. It also identifies risks and unknowns, suggesting specific spikes or investigations to thoroughly examine the codebase and OpenSpec contexts.

The main limitation of using a thinking partner for requirement refinement is that it cannot write code or implement features. If you request implementation, you must exit explore mode first and initiate a change using commands like /opsx:new or /opsx:ff.