openspec-explore

To brainstorm and clarify software requirements, you can use a guided exploration partner that asks open-ended questions and surfaces decision points without writing code. This helps frame problems and elicit requirements before committing to a design.

The best way to explore options for a new feature is entering a non-implementation thinking session. This approach reads your context, asks clarifying questions, and generates design proposals to validate ideas before development begins.

Yes, you can generate optional OpenSpec artifacts during a problem framing session. The exploration partner aids thinking and clarification, and can produce these artifacts if requested to formalize the gathered requirements.

No, this exploration process requires no code execution environment. It functions as a flexible thinking partner that provides open-ended prompts and reads context to help investigate problems across software projects.

You should not use an open-ended thinking partner when you need immediate code generation or automated implementation. It is strictly designed for brainstorming, problem definition, and requirement elicitation before or during change discussions.