openspec-explore

Problem framing involves a collaborative thinking partner to explore ideas, identify risks, and map options visually. This approach reduces ambiguity in early discovery sessions without producing or implementing code.

Requirement discovery is an open-ended reasoning process that surfaces questions and risks before committing to a plan. Visual mapping aids this exploration by clarifying relationships across codebases, architectures, and workflows.

Yes, you can explore codebase architecture changes by iterating on questions, risks, and opportunities. The session acts as a grounded exploration partner that provides visual thinking aids without generating any implementation code.

The best way to compare options and identify risks is through guided open-ended reasoning. This thinking partner helps you evaluate alternatives and map visual relationships during discovery to ensure grounded decisions.

Yes, this exploration approach works for workflow analysis and problem-solving. It supports open-ended reasoning across workflows, helping you surface questions and map options to reduce ambiguity before making decisions.