openspec-explore

Codebase exploration to clarify requirements without writing code is facilitated by structured thinking and open-ended questioning. This approach reads context, maps architecture, and surfaces patterns relevant to your discussions while enforcing no code changes.

Mapping problem spaces during discovery is best handled by using a thinking partner to surface multiple directions. This method applies structured thinking and open-ended questioning to investigate ideas, visualize freely, and clarify the problem space.

You can create OpenSpec proposals and designs during requirements discovery when explicitly requested. This optional artifact creation captures the structured thinking output without proceeding into actual code implementation or changes.

Yes, this approach enforces strict no code changes while investigating the codebase. It isolates exploratory thinking and architecture mapping from implementation, ensuring the primary output remains structured thought and requirements clarification.

Use a thinking partner during the discovery phase to investigate problems, clarify requirements, and surface multiple directions before writing code. It prevents premature implementation by emphasizing structured thinking and problem visualization as the primary output.