openspec-explore

To explore ideas and clarify requirements before implementation, use a thinking partner to guide brainstorming, frame problems, and sketch visual maps of multiple directions. This prevents premature coding by surfacing assumptions and refining questions first.

An OpenSpec exploration posture for brainstorming actively discourages implementation tasks like writing or executing code. Instead, it focuses on adaptive ideation to generate proposals, designs, or specs, helping you investigate questions and map out approaches.

Yes, you can use ASCII visualizations to clarify thinking and map multiple directions during problem framing. This visual approach helps structure your brainstorming, surface hidden assumptions, and sketch potential approaches before making any changes.

No, this exploration mode does not write or execute code. It maintains a non-implementation posture to keep you focused on deep thinking, guided ideation, and flexible exploration, ensuring you fully clarify requirements before acting.

The best way to surface assumptions when planning a new feature is to engage an adaptive exploration partner. It helps you investigate questions, frame the problem clearly, and explore multiple directions, producing structured outputs like proposals or designs.

You need a thinking partner instead of a coding assistant when you are in the early stages of planning a feature and must clarify requirements, frame problems, and explore ideas. It stops premature implementation by focusing solely on generating specs and designs.