openspec-explore

To explore ideas and clarify requirements without writing production code, use a thinking partner approach for guided ideation, problem framing, and collaborative reasoning to surface assumptions and alternative directions.

The best way to frame problems and visualize architecture during early discovery is through collaborative reasoning sessions that read codebases and surface multiple directions, ensuring your thinking is documented rather than implemented.

Yes, you can create OpenSpec proposals, designs, and specs to document your thinking without applying changes, as the exploration process operates within OpenSpec contexts and requires no code execution.

Yes, this requirements exploration approach works entirely without executing code, acting strictly as a thinking partner to investigate problems, read codebases, and refine requirements while must not write or apply production changes.

You should not use a thinking partner for codebase exploration when you need to implement changes, write code, or apply production updates, as its sole purpose is early discovery, problem framing, and requirements refinement.

To start an OpenSpec requirements refinement session, enter explore mode and begin thinking through your project requirements by asking questions, requesting architecture diagrams, or proposing OpenSpec artifacts without writing code.