openspec-explore

To clarify requirements before writing code, use a thinking partner to read context, ask clarifying questions, and surface multiple directions for early-stage problem framing without implementing changes.

The best way to visualize concepts during design conversations is by generating ASCII diagrams within a guided exploration session to safely reason through codebase and product workflow ideas.

Yes, you can discover requirements without modifying your codebase by using a safe reasoning mode that reads context and surfaces risks while strictly avoiding writing code or making changes.

Start a thinking session for early-stage problem framing by instructing the assistant to enter explore mode, which initiates the requirement discovery and design conversation workflow.

This approach works for both process workflows and codebase concepts, applying exploratory reasoning to investigate problems and clarify requirements across product concepts and design conversations.

Avoid using a thinking partner for problem solving when you need direct code writing or immediate implementation changes, as it focuses on safe exploratory reasoning and surfacing options rather than editing.