openspec-explore

To explore and clarify requirements before writing code, you need a thinking partner that facilitates open-ended sessions to surface questions and investigate problems without implementing features. This approach uses flexible questioning and visual aids to help you understand the problem space deeply.

Yes, you can visualize codebase architecture and data flows without executing code by using ASCII diagrams during exploratory thinking sessions. This allows you to map out structures and discuss ideas risk-free while reading files and searching code.

The best way to investigate a codebase for design surface analysis is through guided exploration that checks context and surfaces risks. This method helps you understand the existing architecture by reading files and discussing findings rather than making changes.

Yes, exploratory thinking helps with proposing artifacts like designs and proposals by maintaining OpenSpec-awareness throughout the session. It checks context and suggests these artifacts when appropriate, ensuring your exploration aligns with project requirements.

The primary limitation of using a thinking partner for problem exploration is that it strictly prohibits writing code or executing changes. You can read files, search code, and discuss ideas, but implementation is not allowed to encourage risk-free exploration.

To start an open-ended exploration session for problem understanding, begin by stating your goals and asking clarifying questions. This initiates a guided process where the partner surfaces questions, explores multiple directions, and visualizes data flows.