openspec-explore

To explore ideas and clarify requirements, you need a conversational thinking partner that surfaces multiple directions, challenges assumptions, and maps the problem space without writing code. This approach uses adaptive dialogue to help you investigate implications thoroughly before development begins.

The best way to investigate a codebase for integration points is through guided exploration that maps architecture and identifies existing patterns. This method acts as a thinking partner to help you navigate complex code structures and understand how new changes will interact with current components.

To compare implementation options and visualize tradeoffs, you brainstorm approaches and sketch them using ASCII diagrams. This process highlights the strengths and weaknesses of each potential strategy, enabling you to make informed design decisions through conversational analysis.

Yes, you can use conversational design thinking to capture insights into OpenSpec artifacts. During your exploratory sessions, the thinking partner can optionally map your clarified requirements and architectural investigations directly into structured OpenSpec formats.

No, this approach does not write or modify code during the problem solving process. It operates strictly as a thinking partner focused on requirements clarification, codebase investigation, and option comparison, leaving the actual implementation to other tools or manual development.

You should use exploratory thinking instead of jumping straight into coding when you need to understand the implications of a new feature, clarify vague requirements, or compare potential implementation strategies. It prevents rework by ensuring the problem space is fully mapped before committing to a solution.