openspec-explore

To explore requirements and clarify ideas, you can use an interactive thinking partner that asks clarifying questions, challenges assumptions, and visualizes concepts using ASCII diagrams to map out the problem space before development begins.

You investigate codebase architecture by mapping existing structures, finding integration points, and surfacing complexity within the project, which helps you understand current patterns and visualize potential approaches for new features.

The best way to compare options is by using a thinking partner to evaluate different approaches within your system, grounding the comparison in your actual codebase to surface architectural implications and complexity.

Yes, you can visualize concepts and architecture using ASCII diagrams during problem solving to map structures, identify integration points, and clarify potential approaches before committing to any code implementation.

Yes, this requirements exploration approach works without specific dependencies, acting as a standalone thinking partner to facilitate deep exploration of ideas, problems, and requirements within the OpenSpec system.

You should not use a thinking partner for codebase investigation when you need automated code generation or execution rather than interactive exploration, as it focuses on clarifying requirements and visualizing concepts rather than writing actual code.