openspec-explore

To investigate requirements and clarify design tradeoffs safely, you can use an exploratory reasoning mode that acts as a thinking partner to surface unknowns, compare approaches, and visualize concepts without implementing features.

The best way to explore a codebase during ambiguous planning is using a structured inquiry mode that reads existing OpenSpec context and related artifacts to ground your investigation while maintaining guardrails against implementation.

Yes, you can compare multiple design options and surface risks within OpenSpec workflows by applying structured exploratory reasoning to evaluate tradeoffs, clarify what is needed, and reduce ambiguity before making design decisions.

To visualize concepts and diagram ideas during mid-change debugging, you engage in structured inquiry that leverages existing OpenSpec context, allowing you to map out problem spaces and evaluate implementation options safely.

No, openspec explore mode forbids feature implementation by maintaining strict non-implementation guardrails, allowing only research, requirements clarification, and artifact creation to ensure you think safely through changes before acting.

You need a thinking partner for requirements clarification when facing ambiguous planning, mid-change debugging, or evaluating multiple design options, ensuring you understand the problem space and tradeoffs before committing to code.