openspec-explore

To explore problem space and frame requirements, use a thinking partner to investigate problems, surface risks, and clarify dependencies without writing code. It helps visualize ideas through guided reasoning and prompts.

The best way to visualize ideas and surface risks is using a non-implementation thinking mode that avoids executing tasks. It acts as an AI partner to ask clarifying questions and map out alternative approaches.

Yes, you can clarify project requirements without writing code because this operates in a non-implementation thinking mode. It focuses entirely on problem framing, risk surfacing, and asking clarifying questions.

To start requirements discovery, activate the exploration mode and prompt the AI to think aloud about your project. It will guide the conversation by surfacing questions and visualizing alternative approaches.

Yes, this thinking partner approach works across different teams for early design conversations. It provides guided reasoning to surface dependencies and frame problems regardless of the specific project context.

Use a non-implementation thinking mode to prevent the AI from prematurely writing code or executing actions. It strictly focuses on visualizing ideas, asking clarifying questions, and surfacing risks during problem framing.