openspec-explore

To explore ideas and clarify requirements, you use a thinking partner that maps the problem space and surfaces options without writing code. This approach facilitates early-stage problem framing by investigating risks and structuring decisions before implementation begins.

The best way to investigate a codebase without modifying it is to use an exploration mode that reads and maps the project structure. This allows you to surface questions and risks across domains while ensuring no implementation actions are executed.

Yes, you can visualize design options and problem framing using ASCII diagrams. This feature supports structured decision-making by allowing you to diagram ideas and surface multiple directions during early-stage codebase investigation.

Yes, this requirements exploration approach works completely without dependencies. It operates as a standalone thinking partner to map problem spaces and capture artifacts on demand across various projects and domains.

You should not use a thinking partner for problem framing when you are ready to write or modify code. This approach strictly prohibits implementation actions and is designed only for exploring ideas, surfacing risks, and clarifying requirements.