openspec-explore

To clarify ambiguous requirements, you can use a thinking partner to map problem spaces, surface risks, and articulate constraints, producing structured document artifacts without committing to implementation.

The best way to explore multiple approaches is to reason through ideas, visualize options, and document insights, ensuring alignment on next steps before actual development begins.

Yes, you need the OpenSpec CLI installed to map problem spaces and constraints, as it provides the exploration mode required to guide thinking and surface risks as document artifacts.

No, you cannot use this to generate code, because it strictly guides thinking, surfaces risks, and clarifies needs rather than implementing features or writing codebase logic.

To inspect current changes before starting an exploration session, run openspec list --json to review context and understand the baseline state of your codebase.