openspec-explore

To explore ideas before writing code, you need a thinking partner that surfaces questions and design considerations grounded in your codebase context, separating exploration from implementation without writing code.

Framing early-stage problems using codebase context involves applying exploration mode to investigate the problem space, clarify requirements, and surface alternative directions while keeping thinking time isolated from execution.

Yes, you can use OpenSpec to generate diagrams and surface multiple design directions. It acts as a thinking partner that provides safe thinking guidance and explicitly avoids writing code during the discovery phase.

Yes, this requirements discovery approach is specifically designed for early-stage problem spaces. It helps teams clarify requirements and investigate problems by surfacing relevant questions and directions before implementation begins.

You should not use an exploration thinking partner when you are ready to implement code. It is designed strictly for thinking through changes, clarifying requirements, and isolating thinking time from execution, rather than generating scripts.

You separate thinking time from execution by entering an exploration mode that focuses on design discussions and ideation. This approach surfaces questions and directions while ensuring no code is written during the thinking phase.