openspec-explore

To frame open-ended problems, you can use an exploration mode that prompts questions, visualizes options, and tracks multiple thinking threads to surface design choices without forcing a direction. This clarifies requirements early.

Brainstorming architecture options is best supported by a thinking partner that enforces non-prescriptive exploration, helping you surface risks, map threads, and outline potential approaches before any codebase changes occur.

Yes, you can visualize multiple exploration threads during early-stage strategy. The exploration process explicitly supports multi-thread thinking and visualizations to help teams map alternatives and align on problem framing.

You start an open-spec exploration session by entering the exploration mode using the command /opsx:explore, which initiates the non-prescriptive reasoning ally to guide your team through problem framing.

No, the problem framing process does not enforce changes to the codebase. It operates in a strictly non-prescriptive exploration mode, surfacing questions, risks, and design options without performing any modifications.

You should use an exploration ally instead of writing solutions when your team struggles to align on requirements, needing to map exploration threads and clarify next steps before committing to a specific implementation direction.