openspec-explore

To clarify requirements without modifying the codebase, use a thinking partner approach that reads context, poses clarifying questions, and surfaces options. This prevents code changes while mapping dependencies and risks during early discovery.

The best way to investigate codebase dependencies during early discovery is by reading context and diagrams to map dependencies and visualize risks. This codebase grounding approach aids exploration by generating ASCII diagrams and decision surfaces.

To frame problems and surface multiple directions without prescribing a single path, enter an exploration mode that acts as a thinking partner. This approach surfaces questions, edges, and options while preventing code edits, focusing entirely on requirement clarification.

Yes, you can create OpenSpec proposals, designs, and specs while exploring requirements. This is considered capturing thinking rather than implementing code, so it is fully allowed even when code changes are strictly prevented.

You should not use this exploration approach when you need to implement features or write code. If the user asks to implement something, they must exit explore mode first and create a change proposal to proceed with actual coding tasks.

Yes, OpenSpec explore mode supports generating visualizations for complex problems. It generates ASCII diagrams and decision surfaces to aid exploration, helping teams visualize ideas and map dependencies while acting as a thinking partner.