openspec-explore

To explore ideas and clarify requirements, use a guided thinking partner that reads your codebase, asks questions, and surfaces visual diagrams. This approach frames problems during early discovery without writing any implementation code.

The best way to frame design discussions is by grounding the conversation in your codebase to surface risks and propose speculative artifacts. This deep thinking process provides prompts and visual diagrams while keeping the exploration strictly conceptual.

Yes, you can visualize codebase risks and options without implementing changes by generating speculative artifacts and diagrams. The process adheres to a strict no-implementation policy, providing only prompts and visual models for your exploration.

Yes, you need the OpenSpec CLI context to start a guided design discussion. The thinking partner requires this environment to read your codebase accurately and ground its exploratory questions and visual diagrams in your actual project structure.

To use a thinking partner for early discovery, enter explore mode to begin deep thinking about your idea. The partner analyzes your codebase, asks clarifying questions, and provides visual diagrams to help you articulate requirements before development.

The limitation of a no-implementation policy for codebase exploration is that the tool will not write or modify code. It only provides prompts, diagrams, and speculative artifacts, meaning you must implement the actual changes separately after the design discussion.