openspec-explore

To explore requirements and visualize solutions before writing code, use a guided thinking partner that reads codebase context, surfaces risks, and maps problem paths using ASCII diagrams without performing implementations.

Yes, you can investigate your codebase for context without executing changes. The thinking partner reads files and analyzes dependencies to discuss options while maintaining a strict non-implementation stance.

The best way to surface unknown risks during problem-space exploration is to structure conversations around context and decisions, allowing a thinking partner to illuminate potential pitfalls and prompt for artifact capture early.

Yes, OpenSpec exploration supports ASCII diagrams for design visualization. It leverages these diagrams alongside risk surfacing to help teams map paths and clarify requirements during the exploration phase.

To map options and ask clarifying questions for a new software design, describe the problem you want to explore. The partner will help visualize paths, surface dependencies, and structure the design surface.

You should not use a thinking partner for codebase investigation when you need to write, execute, or deploy code. It focuses entirely on thinking, design, and problem framing rather than performing implementations.