openspec-explore

To clarify requirements, use a thinking-partner mode that explores ideas, surfaces clarifying questions, and maps the problem space before implementation begins. This approach enforces a non-implementation stance to help you frame early-stage problems and identify risks.

Exploring open-ended design problems works best with an adaptive thinking partner that investigates possibilities, prompts for clarifying questions, and uses ASCII diagrams for visual thinking. This keeps exploration flexible without dictating a specific path.

Yes, a thinking-partner approach is specifically suited for early-stage problem framing and requirement elicitation. It maintains a curious, adaptive stance to surface unknowns, identify risks, and outline potential next steps for informed decision making.

To surface risks during requirement elicitation, engage in an exploration mode that prompts clarifying questions and visualizes the problem space. This process highlights unknowns, potential risks, and next steps to inform your decision making.

Yes, requirement exploration enforces a strict non-implementation stance to prevent premature coding. By focusing entirely on problem framing, clarifying questions, and visual thinking with ASCII diagrams, it ensures the problem space is fully mapped first.

You should not use an exploring partner when you need to implement solutions or write code, as it strictly enforces a non-implementation stance. It is designed only for early-stage problem framing, requirement elicitation, and design exploration.