openspec-explore

To explore ideas and clarify requirements without writing code, you need a thinking partner that reads files, analyzes options, and visualizes outcomes. This approach surfaces risks and unknowns early, keeping problem framing grounded without implementing features.

The best way to frame complex problems before a software design is using structured prompts and visual exploration. This method guides teams through early discovery, surfacing unknowns and visualizing ideas with diagrams to ensure deep thinking captures all constraints.

Yes, you can generate OpenSpec artifacts like proposals, designs, and specs on demand during problem framing. This captures your team's thinking and exploration results without forcing you to implement any code changes or follow rigid sequences.

You can visualize technical options and surface risks during early project discovery by using ASCII diagrams and structured exploration. An adaptive thinking partner analyzes your codebase and requirements, presenting visual outputs that highlight unknowns and open threads.

Yes, this requirements exploration approach works for investigating an existing codebase. It reads files and searches code to inform decisions, acting as a patient thinking partner that analyzes the current state without writing or modifying any implementation code.