openspec-explore

Structured exploratory thinking for codebase analysis is facilitated by guiding users through problem framing, inquiry, and design exploration. It helps surface dependencies, risks, and assumptions before committing to changes.

Problem framing before software design exploration is best handled by a thinking partner that encourages questions and multiple directions. This approach clarifies requirements and outlines safe thinking workflows using Dewey-guided tools.

To clarify requirements and surface assumptions during project exploration, open-thread exploration is used. It links related documents and code references to provide contextual Dewey-driven guidance for thinking through alternatives.

Design thinking sessions can be used for exploring requirements across multiple domains. The process applies a curated thinking stance that encourages visual thinking and inquiry to achieve clarity before any action is taken.

No specific dependencies are required to run structured thinking workflows for problem framing. The process operates independently to outline Dewey-guided tools and generate optional artifacts for safe thinking workflows.

You should use a thinking partner instead of jumping straight into coding when facing complex problems requiring deep exploration. It helps you think through alternatives, clarify requirements, and establish guardrails before committing to changes.