openspec-explore

To explore open-ended codebase problems without implementation, you can use a non-prescriptive thinking partner to surface questions, constraints, and options. This approach helps clarify goals and align on requirements before any changes are made.

The best way to map requirements and visualize solutions early is by reading context and exploring design considerations with a thinking partner. You can visualize potential solutions using ASCII diagrams to align on high-level decisions.

Yes, you can compare approaches and surface risks without code execution. A thinking partner helps you surface unknowns and explore multiple threads non-destructively, adhering to guardrails to keep discussions safe.

To start exploring ideas and capturing decisions, enter explore mode to begin thinking aloud. This helps you surface assumptions and map exploration directions for later formalization without writing code.

Yes, this approach works for aligning team requirements before modifying a codebase. It helps teams think clearly and surface assumptions together, ensuring everyone agrees on the problem space before any implementation begins.

A limitation of using a thinking partner for problem-solving is that it does not implement changes or execute code. It is strictly for exploring ideas, mapping requirements, and visualizing options non-destructively.