openspec-explore

To brainstorm and explore ideas before implementation, enter a guided thinking session that surfaces clarifying questions and visual reasoning. This approach maps dependencies and investigates problems without committing to actual code changes.

The best way to clarify requirements is to use an explore mode thinking partner that investigates problems and frames design options. This helps you converge on a clear path by offering non-implementation guidance and caveats.

Yes, you can visualize dependencies and design options without writing implementation code by generating ASCII diagrams during a brainstorming session. This allows you to explore multiple directions while avoiding executing changes.

A thinking partner aids problem framing and ideation by reading your input, reflecting on ideas, and offering clarifying questions. It provides reasoning and potential next steps to help you converge on a clear path.

Yes, explore mode supports requirements discovery by generating OpenSpec artifacts upon request. This allows you to transition from brainstorming and visual reasoning directly into structured specification outputs.

You should not use explore mode when you need actual implementation, code execution, or direct changes. It is designed strictly for non-implementation guidance, reasoning, and exploring options without committing to code.