openspec-explore

You clarify requirements during early project discovery by exploring ideas with a thinking partner that surfaces risks, unknowns, and decisions through targeted questions and visual diagrams.

Framing an open-ended problem is best handled by a structured exploration process that enforces non-implementation rules, using ASCII diagrams and context checks to map possible paths before coding begins.

Yes, you can use ASCII diagrams to visualize risks and decisions, as the exploration process actively promotes visual thinking to help surface multiple threads and possible paths.

Yes, this problem framing approach works without writing code because it enforces strict non-implementation rules, focusing entirely on thinking, capturing questions, and structuring ideas for later review.

A limitation of using a thinking partner for open-ended exploration is that it strictly enforces non-implementation rules, meaning it cannot generate code or execute solutions, only surface risks and capture artifacts.