openspec-explore

To clarify requirements before implementation, you can use a guided thinking partner to explore the problem space, surface questions, and frame specifications without writing code. This approach helps structure early-stage requirement iteration and brainstorming.

Brainstorming problem-space ideas is best done with a non-implementation thinking partner that investigates problems and frames requirements. This allows you to map out decisions and iterate on concepts before any actual development begins.

Yes, you can generate OpenSpec artifacts during requirement planning. When explicitly requested, the exploration session can propose designs, specs, and proposals to capture the reasoning and decisions derived from your brainstorming.

No dependencies or installation are required for this requirements exploration approach. It functions purely as a guided thinking partner that reads files to inform thinking but strictly avoids executing code or implementing features.

Using a thinking partner instead of directly coding ensures thorough problem-space exploration before commitment. It maintains a non-implementation stance to help frame requirements clearly, preventing premature development and capturing design rationale.

You should not use an exploratory thinking partner when your project requires immediate code execution or feature implementation. It strictly avoids writing or running code, focusing solely on requirement framing and early-stage idea exploration.