openspec-explore

To clarify requirements and explore ideas, use a thinking partner that guides problem-space mapping, surfaces risks, and provides visual diagrams to drive decision-making without writing implementation code.

Problem-space mapping is the process of investigating possible approaches, risks, and questions during early discovery. You need it when examining a codebase to surface options and clarify open-ended requirements before implementation.

Yes, you can use visual diagrams to investigate problems and surface risks during discovery. The thinking partner provides non-prescriptive prompts and visual outputs to map the problem space and drive decision-making.

The best way to map out possible approaches for an open-ended problem is engaging a thinking partner that provides structured prompts, visualizes the problem space, and surfaces risks to guide your exploration and decision-making.

The thinking partner provides only non-implementation guidance. It focuses on exploring ideas, investigating problems, and clarifying requirements without generating code, keeping the session strictly within open-ended discovery workflows.

You should not use an exploration session when you need actual code implementation rather than discovery. This thinking partner is designed strictly for problem-space mapping, risk surfacing, and requirements clarification, not for writing or deploying code.