openspec-explore

To clarify requirements before writing code, you can use an exploration mode that acts as a thinking partner, asking questions and visualizing options without modifying your codebase. It reads project context to ground the discussion in your actual files.

Mapping open-ended problems involves surfacing alternatives, dependencies, and design directions through guided questions. An adaptive thinking partner helps structure this discovery phase, ensuring you identify risks before committing to a specific solution.

Yes, you can read codebase files during requirement discovery sessions to ground your understanding. The exploration mode inspects project context and files as needed, ensuring the design discussion remains aligned with your existing architecture.

To start a problem definition session without committing to code changes, simply describe the idea you want to explore. The system will begin by asking clarifying questions to map the problem space and visualize potential options.

Yes, exploration mode works for visualizing dependencies while remaining non-intrusive to your code. It provides a guided space to inspect project context and surface design risks without writing code or altering existing files.

You should use a thinking partner when facing open-ended problems or ambiguous requirements before or during changes. It helps clarify the problem definition and gather context, preventing premature commitment to an unsuitable technical solution.