openspec-explore

A thinking partner helps you explore ideas and clarify requirements by reading your codebase, reasoning about designs, and surfacing questions to shape potential OpenSpec artifacts without implementing changes.

Visualizing a problem space involves articulating goals, reading relevant codebase structures, and surfacing questions or diagrams to capture the design thinking process and outline potential exploration paths.

Yes, you can read and reason about codebases or designs without implementing changes. The focus remains on open-ended discussion to investigate problems and capture requirements rather than modifying code.

Describe your goal to start an open-ended exploration. The thinking partner will then analyze the problem space, read relevant codebase sections, and surface questions along with potential OpenSpec artifacts to guide direction.

Use a thinking partner when you need to think through something before or during a change. It helps investigate problems, clarify requirements, and surface OpenSpec artifacts rather than immediately writing code.