openspec-explore

To explore ideas and clarify requirements, you need a thinking partner that guides problem framing, surfaces clarifying questions, and uses visual thinking without performing implementations. This approach enforces guardrails during brainstorming sessions to ensure thorough design exploration.

The best way to investigate problems and frame design thinking is by entering an exploration mode that prompts open-ended inquiry. It surfaces risks, dependencies, and next steps across projects and codebases, helping you think deeply before making structural decisions.

To create OpenSpec artifacts during brainstorming, use a guided exploration process that clarifies requirements and frames problems. It guides the creation of these artifacts by enforcing guardrails and prompting questions without directly writing or modifying implementation code.

Yes, you can use ASCII diagrams to visualize requirements and problem framing. The exploration process encourages visual thinking, allowing you to map out ideas, investigate dependencies, and clarify complex problems visually during your design sessions.

Yes, this requirements exploration approach works strictly without modifying your codebase. It acts as a thinking partner that enforces guardrails, ensuring you can safely investigate problems, surface risks, and clarify requirements without performing any actual implementations.

You should not use a thinking partner for problem framing when you are ready to execute concrete implementations. This exploration mode is designed specifically for brainstorming, investigating problems, and clarifying requirements, rather than writing or deploying code changes.