openspec-explore

To clarify requirements before coding, you can partner with an AI thinking tool that asks clarifying questions, challenges assumptions, and visualizes concepts with ASCII diagrams to help you reframe the problem and map out risks.

Problem framing and codebase analysis work by investigating your existing code to map architecture, find integration points, and surface patterns, helping you understand the structure and identify potential risks before making changes.

The best way to investigate codebase risks is to use an exploration partner that identifies what could go wrong, surfaces gaps in your logic, and suggests spikes to validate assumptions before you commit to implementation.

Yes, you can use ASCII diagrams liberally during design exploration to clarify concepts, map out architecture, and visualize integration points without writing any actual implementation code.

No, this requirements exploration approach avoids implementing code entirely; it focuses solely on thinking through the problem, asking questions, and only suggests artifacts if you explicitly request them.

You need to explore options and surface risks when you want to think through a design or change beforehand, allowing an AI partner to assess your codebase, investigate problems, and clarify requirements before taking action.