openspec-explore

To explore problem space before writing code, use a thinking partner to surface assumptions, frame the problem, and map dependencies without implementing any solutions. It helps align scope and surface risks early in the discovery phase.

Framing design discussions benefits from open-ended exploration and visual reasoning artifacts like ASCII diagrams. This approach maps ideas and decisions, keeping conversations productive by encouraging questions and surfacing risks without dictating a path.

Yes, you can reason about integrating a new feature without implementing it. The skill enforces a non-implementation workflow, providing stance guidance and structured notes to help you investigate problems and align on scope before any code is written.

Surface assumptions and risks during early discovery by engaging in curious, open-ended exploration. The skill prompts structured thinking to identify multiple directions and potential pitfalls, ensuring you clarify requirements before starting a change.

You should not use an exploration thinking partner when you are ready to write or implement code. The workflow strictly enforces non-implementation, focusing entirely on problem framing, visual reasoning, and requirement clarification.