openspec-explore

To frame problems before committing to code changes, use a structured thinking partner to surface questions, map assumptions, and compare options. This pre-change exploration clarifies constraints and gathers evidence across documents and architecture.

The best way to gather evidence during problem framing is to interact with a thinking partner that cross-references documents, code, and architecture. This ensures your exploration is grounded in existing system structures before proposing changes.

Yes, you can generate OpenSpec artifacts without implementation. The exploration process ensures safe, non-implementation reasoning, providing guidance to produce proposals, designs, or tasks only when requested.

Yes, this thinking partner approach works for visualizing reasoning and comparing architectural options. It structures the exploration of questions and offers lightweight summaries to map out the decision space.

You should not use structured exploration when you need immediate implementation rather than problem framing. This process focuses on weighing options and gathering evidence pre-change, intentionally avoiding direct code generation or system modification.