openspec-explore

To explore ideas and clarify requirements before implementation, you need a thinking partner that applies curious, non-prescriptive questioning to surface multiple directions and keep conversations open. This approach ensures deeper understanding of problems before acting on decisions.

The best way to investigate problem framing safely is through non-implementation exploration that surfaces OpenSpec artifacts like proposals, designs, and specs when needed. This method provides a thinking partner to investigate problems without executing any code changes.

Yes, you can visualize dependencies and lightweight models using ASCII diagrams during requirements gathering. This visual thinking approach helps illustrate ideas clearly, enabling deeper understanding of the problem space before making implementation decisions.

Yes, think-aloud exploration works effectively across early design, requirements gathering, and problem framing contexts. It provides safe, exploratory reasoning to clarify requirements and investigate problems by asking non-prescriptive questions that keep conversations open.

To start a guided exploration session, enter explore mode to think deeply with a partner that applies curious questioning and visual thinking. This process clarifies requirements and investigates problems through non-prescriptive, open conversation before any implementation begins.

The main limitation of this non-prescriptive thinking partner is that it performs safe, exploratory reasoning only and does not execute code changes. It focuses entirely on clarifying requirements and surfacing OpenSpec artifacts, leaving actual implementation to separate actions.