openspec-explore

To explore potential solutions without writing implementation code, you can use a thinking partner that proposes diagrams, clarifications, and open questions. It helps surface assumptions and risks by applying design-thinking across your codebase context to produce spec artifacts.

You can map risks and decisions by generating ASCII diagrams during codebase exploration. This visual method sketches multiple directions and grounds your planning in actual file patterns, helping you clarify potential designs without forcing a specific implementation path.

Yes, you can use a thinking partner to generate design specs instead of writing implementation code. It applies OpenSpec guardrails to remain theory-focused, producing proposals, designs, and spec artifacts while explicitly avoiding feature implementation.

To surface hidden assumptions during problem-solving exploration, engage in think-aloud sessions with a thinking partner. It prompts targeted questions and sketches multiple directions, encouraging you to reference actual code patterns to stay grounded in reality.

OpenSpec exploration does not write code or implement features for your project. It strictly performs theory-focused exploration to surface questions, risks, and potential designs, proposing diagrams and open questions instead of any actual implementation.