openspec-explore

You explore ideas and clarify requirements by entering a discovery session where an AI guides you through structured thinking, asks probing questions, and surfaces unknowns. This process maps the problem space and reduces ambiguity before any implementation begins.

Brainstorming design discussions across codebases works best by using a thinking partner to read relevant files and suggest hypotheses. This approach visualizes options and captures exploratory artifacts without committing to code changes prematurely.

Yes, you can generate diagrams during a requirements clarification session. The exploration mode maps the problem space by suggesting visual diagrams alongside free-form analysis to help teams think through ideas and inform decision-making.

No, this requirements exploration mode does not write or modify code. It strictly enforces exploration boundaries by focusing on design discussions, outlining questions, and capturing hypotheses, deliberately avoiding all implementation tasks.

You need a thinking partner for feature proposals when you want to surface risks, unknowns, and assumptions early in the discovery process. It helps outline questions and visualize options before committing to actual development.

A key limitation is that this AI brainstorming approach is strictly bounded to exploration and will not execute implementation tasks. If your session requires writing code or making file modifications, you must switch to a different mode.