openspec-explore

To explore ideas and clarify requirements before implementing code, you need a thinking partner that surfaces multiple directions and investigates problems without writing code. This approach uses adaptive conversations to map architecture and visualize tradeoffs.

The best way to analyze codebase architecture and find integration points is by deeply investigating existing patterns within the codebase. This process maps architectural structures and identifies integration points to clarify complex issues before committing to a design.

To compare design options and visualize tradeoffs for a new feature, you brainstorm approaches and sketch the resulting tradeoffs. Visualizing options using ASCII diagrams helps clarify the distinctions between different architectural approaches.

Yes, you can use this approach to capture insights and create OpenSpec artifacts. It supports OpenSpec artifact creation during the thinking process, allowing you to document architectural analysis and requirements clarification directly.

You should not use this exploration method when you need direct code implementation. It acts strictly as a thinking partner to facilitate deep exploration of ideas and problems, meaning it will analyze and visualize but will not write the actual code.