openspec-explore

To clarify requirements before coding, use an exploration mode that acts as a thinking partner to map the problem space and surface open-ended questions. This approach grounds discussions in your codebase to align teams and identify risks early.

The best way to frame problems during early design discussions is through structured prompts and context grounding. This ensures conversations remain focused on discovering risks and synthesizing decisions rather than jumping into implementation details.

To surface unknown risks across your codebase and product concepts, engage a thinking partner that uses structured inquiry to map options. It identifies potential failure points and captures synthesis for later decisions safely.

Yes, you can use open-spec exploration for codebase grounding without writing code. It enforces safe, non-implementation exploration by referencing relevant files and patterns to anchor your early design discussions in reality.

You should not use a thinking partner for requirement exploration when you need direct implementation or code generation. This approach strictly enforces non-implementation exploration, making it unsuitable for tasks requiring immediate software engineering output.