openspec-explore

You can clarify requirements without writing code by entering an exploratory mode that asks open-ended questions to surface multiple directions. This AI-driven approach helps you think through ideas and investigate problems while remaining in a non-prescriptive dialogue.

Yes, you can explore an existing codebase during early design discussions because the environment reads files and searches the repository. It maintains codebase awareness while staying in explore mode to help you investigate problems without implementing code.

To generate diagrams and visual aids for requirement gathering, you can use the explore mode to create ASCII diagrams, comparison tables, and risk mappings. These visual outputs help structure your investigation and make complex ideas easier to understand.

The best way to capture brainstorming insights into OpenSpec artifacts is to use the explore mode, which suggests capturing your clarified requirements directly into proposals, designs, or specs. This ensures your exploratory dialogue translates into structured documentation.

Yes, the OpenSpec CLI environment supports exploring ideas before implementation by providing an AI-driven exploratory mode. It operates within the CLI, reads files, searches code, and facilitates requirement gathering without committing to code changes.

You should not use an exploratory mode when you need to implement code rather than clarify requirements. This mode focuses on early design discussions, brainstorming, and investigating problems, meaning it will not generate or execute code for your project.